CVE-2016-0640: Medium severity mysql vulnerability
Unspecified vulnerability in Oracle MySQL 5.5.47 and earlier, 5.6.28 and earlier, and 5.7.10 and earlier and MariaDB before 5.5.48, 10.0.x before 10.0.24, and 10.1.x before 10.1.12 allows local users to affect integrity and availability via vectors related to DML.
Other sources
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DML). Supported versions that are affected are 5.5.47 and earlier, 5.6.28 and earlier and 5.7.10 and earlier. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data.
External References:
http://www.oracle.com/technetwork/topics/security/cpuapr2016verbose-2881709.html
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2016-0640?
CVE-2016-0640 has been rated with a medium severity, as it can impact the integrity and availability of databases.
How do I fix CVE-2016-0640?
To fix CVE-2016-0640, upgrade MySQL or MariaDB to version 5.5.48, 5.6.29, 5.7.11 or corresponding patched versions.
Which versions are affected by CVE-2016-0640?
CVE-2016-0640 affects MySQL versions 5.5.47 and earlier, 5.6.28 and earlier, 5.7.10 and earlier, as well as several versions of MariaDB.
What types of issues can CVE-2016-0640 cause?
CVE-2016-0640 can potentially allow local users to affect the integrity and availability of the database server.
Is there a workaround for CVE-2016-0640?
There is no known workaround for CVE-2016-0640, so patching to a secure version is essential.