CVE-2016-6662: Critical severity mysql vulnerability
Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.27, and 10.1.x before 10.1.17; and Percona Server before 5.5.51-38.1, 5.6.x before 5.6.32-78.0, and 5.7.x before 5.7.14-7 allow local users to create arbitrary configurations and bypass certain protection mechanisms by setting generallogfile to a my.cnf configuration. NOTE: this can be leveraged to execute arbitrary code with root privileges by setting malloclib. NOTE: the affected MySQL version information is from Oracle's October 2016 CPU. Oracle has not commented on third-party claims that the issue was silently patched in MySQL 5.5.52, 5.6.33, and 5.7.15.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2016-6662?
CVE-2016-6662 is classified as a medium severity vulnerability that could allow local users to create arbitrary configurations.
Which versions of MySQL are affected by CVE-2016-6662?
CVE-2016-6662 affects Oracle MySQL versions 5.5.52 and earlier, 5.6.x versions prior to 5.6.33, and 5.7.x versions prior to 5.7.15.
How can I mitigate CVE-2016-6662?
To mitigate CVE-2016-6662, upgrade to the latest version of MySQL or apply the relevant patches provided by Oracle.
Are MariaDB versions affected by CVE-2016-6662?
Yes, CVE-2016-6662 impacts MariaDB versions before 5.5.51, 10.0.x before 10.0.27, and 10.1.x before 10.1.17.
What impact does CVE-2016-6662 have on Percona Server?
CVE-2016-6662 affects Percona Server versions before 5.5.51-38.1, 5.6.x before 5.6.32-78.0, and 5.7.x before 5.7.14-7.