First published: Thu Apr 21 2016(Updated: )
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.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/mysql | <5.5.48 | 5.5.48 |
redhat/mysql | <5.6.29 | 5.6.29 |
redhat/mysql | <5.7.11 | 5.7.11 |
redhat/mariadb | <5.5.48 | 5.5.48 |
redhat/mariadb | <10.1.12 | 10.1.12 |
redhat/mariadb | <10.0.24 | 10.0.24 |
Oracle MySQL | >=5.5.0<=5.5.47 | |
Oracle MySQL | >=5.6.0<=5.6.28 | |
Oracle MySQL | >=5.7.0<=5.7.10 | |
Oracle Linux | =7 | |
SUSE Linux | =42.1 | |
MariaDB | >=5.5.20<5.5.48 | |
MariaDB | >=10.0.0<10.0.24 | |
MariaDB | >=10.1.0<10.1.12 | |
Debian | =8.0 | |
Red Hat Enterprise Linux | =6.0 | |
Red Hat Enterprise Linux | =7.0 | |
IBM PowerKVM | =2.1 | |
IBM PowerKVM | =3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-0640 has been rated with a medium severity, as it can impact the integrity and availability of databases.
To fix CVE-2016-0640, upgrade MySQL or MariaDB to version 5.5.48, 5.6.29, 5.7.11 or corresponding patched versions.
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.
CVE-2016-0640 can potentially allow local users to affect the integrity and availability of the database server.
There is no known workaround for CVE-2016-0640, so patching to a secure version is essential.