CVE-2016-5507
First published: Tue Oct 25 2016(Updated: )
Unspecified vulnerability in Oracle MySQL 5.6.32 and earlier and 5.7.14 and earlier allows remote administrators to affect availability via vectors related to Server: InnoDB.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle MySQL Installer | >=5.6.0<=5.6.32 | |
| Oracle MySQL Installer | >=5.7.0<=5.7.14 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-5507?
CVE-2016-5507 has not been assigned a specific CVSS score, but it affects the availability of Oracle MySQL.
How do I fix CVE-2016-5507?
To fix CVE-2016-5507, upgrade to MySQL versions 5.6.33 or later and 5.7.15 or later.
Which versions of MySQL are affected by CVE-2016-5507?
CVE-2016-5507 affects Oracle MySQL versions 5.6.32 and earlier, as well as 5.7.14 and earlier.
Is CVE-2016-5507 a remote vulnerability?
Yes, CVE-2016-5507 allows remote administrators to affect the availability of the MySQL server.
What component of MySQL is impacted by CVE-2016-5507?
CVE-2016-5507 relates specifically to the InnoDB storage engine within Oracle MySQL.
- agent/type
- agent/remedy
- agent/author
- agent/references
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/oracle
- canonical/oracle mysql
- version/oracle mysql/5.6.0
- version/oracle mysql/5.6.32
- version/oracle mysql/5.7.0
- version/oracle mysql/5.7.14