CVE-2016-5630: Medium severity oracle mysql vulnerability
Published Oct 25, 2016
·Updated
Unspecified vulnerability in Oracle MySQL 5.6.31 and earlier and 5.7.13 and earlier allows remote administrators to affect availability via vectors related to Server: InnoDB.
Affected Software
3 affected components
ORACLE MySQL>=5.6.0<=5.6.31
ORACLE MySQL>=5.7.0<=5.7.13
MariaDB MariaDB>=10.0.0<10.0.27
Remediation
Event History
Oct 25, 2016
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2016-5630?
CVE-2016-5630 is considered a high severity vulnerability due to its potential impact on the availability of Oracle MySQL.
2
How do I fix CVE-2016-5630?
To fix CVE-2016-5630, users should upgrade their Oracle MySQL installations to version 5.6.32 or later, or 5.7.14 or later.
3
What versions of MySQL are affected by CVE-2016-5630?
CVE-2016-5630 affects Oracle MySQL versions 5.6.31 and earlier and 5.7.13 and earlier.
4
Does CVE-2016-5630 affect MariaDB installations as well?
Yes, CVE-2016-5630 affects MariaDB versions earlier than 10.0.27.
5
Can CVE-2016-5630 be exploited by remote attackers?
Yes, CVE-2016-5630 can be exploited by remote administrators, potentially affecting the system's availability.