First published: Wed Jan 17 2018(Updated: )
Last updated 24 July 2024
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/mysql | <5.6.39 | 5.6.39 |
redhat/mysql | <5.7.21 | 5.7.21 |
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 | ||
Oracle MySQL | >=5.6.0<=5.6.38 | |
Oracle MySQL | >=5.7.0<=5.7.20 | |
MariaDB | >=10.0.0<10.0.34 | |
MariaDB | >=10.1.0<10.1.31 | |
MariaDB | >=10.2.0<10.2.13 | |
NetApp Active IQ Unified Manager | >=7.3 | |
NetApp Active IQ Unified Manager for VMware vSphere | >=9.5 | |
NetApp OnCommand Insight | ||
NetApp OnCommand Workflow Automation | ||
NetApp SnapCenter | ||
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
Ubuntu | =17.10 | |
Debian | =8.0 | |
Debian | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-2612 is considered easily exploitable with a high severity impact, allowing a high privileged attacker network access.
To fix CVE-2018-2612, upgrade MySQL Server to version 5.6.39 or later, or to version 5.7.21 or later.
MySQL versions 5.6.38 and prior, as well as 5.7.20 and prior, are vulnerable to CVE-2018-2612.
Yes, MariaDB versions prior to 10.0.34, 10.1.31, and 10.2.13 are also affected by CVE-2018-2612.
CVE-2018-2612 exposes the MySQL Server to unauthorized access through multiple network protocols for high privileged attackers.