low
3.5
Advisory Published
CVE Published
Updated

CVE-2018-2767

First published: Mon Apr 09 2018(Updated: )

Last updated 24 July 2024

Credit: secalert_us@oracle.com

Affected SoftwareAffected VersionHow to fix
debian/mariadb-10.0
debian/mysql-5.5
debian/mysql-5.7
redhat/mysql<5.5.61
5.5.61
redhat/mysql<5.6.41
5.6.41
redhat/mysql<5.7.23
5.7.23
redhat/mariadb<5.5.60
5.5.60
redhat/mariadb<10.0.35
10.0.35
redhat/mariadb<10.1.33
10.1.33
redhat/mariadb<10.2.15
10.2.15
redhat/mariadb<10.3.7
10.3.7
Oracle MySQL Installer>=5.5.0<=5.5.60
Oracle MySQL Installer>=5.6.0<=5.6.40
Oracle MySQL Installer>=5.7.0<=5.7.22
Debian=8.0
Debian=9.0
Ubuntu=12.04
Ubuntu=14.04
Ubuntu=16.04
Ubuntu=18.04
redhat openstack=12
Red Hat Enterprise Linux Desktop=7.0
redhat enterprise Linux eus=7.5
redhat enterprise Linux eus=7.6
redhat enterprise Linux eus=7.7
Red Hat Enterprise Linux Server=7.0
Red Hat Enterprise Linux Server=7.6
Red Hat Enterprise Linux Server=7.7
redhat enterprise Linux server tus=7.6
redhat enterprise Linux server tus=7.7
Red Hat Enterprise Linux Workstation=7.0
MariaDB>=5.5.0<5.5.60
MariaDB>=10.0.0<10.0.35
MariaDB>=10.1.0<10.1.33
MariaDB>=10.2.0<10.2.15
NetApp OnCommand Insight
NetApp OnCommand Workflow Automation
NetApp SnapCenter

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2018-2767?

    CVE-2018-2767 is classified with a moderate severity level due to its implications on data transmission security.

  • How do I fix CVE-2018-2767?

    To fix CVE-2018-2767, update the MySQL or MariaDB packages to the recommended versions as outlined in the vulnerability reports.

  • Which applications are affected by CVE-2018-2767?

    CVE-2018-2767 affects MySQL 5.5, MariaDB 5.5, and other specific versions noted in the vulnerability details.

  • What are the risks of not addressing CVE-2018-2767?

    Not addressing CVE-2018-2767 can expose your database connections to potential man-in-the-middle attacks due to the lack of enforced SSL/TLS.

  • Is there a known workaround for CVE-2018-2767?

    A temporary workaround for CVE-2018-2767 includes verifying existing configurations enforce SSL/TLS usage on client connections.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203