7.5
Advisory Published
CVE Published
Updated

CVE-2018-2562

First published: Wed Jan 17 2018(Updated: )

Last updated 24 July 2024

Credit: secalert_us@oracle.com

Affected SoftwareAffected VersionHow to fix
redhat/mysql<5.5.59
5.5.59
redhat/mysql<5.6.39
5.6.39
redhat/mysql<5.7.20
5.7.20
redhat/mariadb<5.5.59
5.5.59
redhat/mariadb<10.2.13
10.2.13
redhat/mariadb<10.1.31
10.1.31
redhat/mariadb<10.0.34
10.0.34
debian/mariadb-10.0
debian/mysql-5.5
debian/mysql-5.7
MySQL>=5.5.0<=5.5.58
MySQL>=5.6.0<=5.6.38
MySQL>=5.7.0<=5.7.19
Mariadb Mariadb>=5.5.0<5.5.59
Mariadb Mariadb>=10.0.0<10.0.34
Mariadb Mariadb>=10.1.0<10.1.31
Mariadb Mariadb>=10.2.0<10.2.13
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
Ubuntu Linux=12.04
netapp active iq unified manager windows>=7.3
NetApp Active IQ Unified Manager for VMware vSphere>=9.5
NetApp OnCommand Insight
NetApp OnCommand Workflow Automation
NetApp SnapCenter
redhat enterprise Linux desktop=7.0
redhat enterprise Linux eus=7.5
redhat enterprise Linux eus=7.6
redhat enterprise Linux eus=7.7
redhat enterprise Linux server=7.0
redhat enterprise Linux server aus=7.6
redhat enterprise Linux server aus=7.7
redhat enterprise Linux server tus=7.6
redhat enterprise Linux server tus=7.7
redhat enterprise Linux workstation=7.0
redhat openstack=12

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.

Reference Links

Frequently Asked Questions

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

    CVE-2018-2562 is rated as easily exploitable, allowing low privileged attackers network access.

  • How do I fix CVE-2018-2562?

    To fix CVE-2018-2562, upgrade MySQL or MariaDB to the respective patched versions: MySQL 5.5.59, 5.6.39, or 5.7.20.

  • Which versions are affected by CVE-2018-2562?

    Affected versions of MySQL include 5.5.58 and prior, 5.6.38 and prior, and 5.7.19 and prior.

  • What components are impacted by CVE-2018-2562?

    CVE-2018-2562 affects the MySQL Server component under the Server: Partition subcomponent.

  • Is there a workaround for CVE-2018-2562?

    There is no known workaround for CVE-2018-2562; applying the security update is the recommended approach.

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