CVE-2016-8288
First published: Tue Oct 25 2016(Updated: )
Unspecified vulnerability in Oracle MySQL 5.6.30 and earlier and 5.7.12 and earlier allows remote authenticated users to affect integrity via vectors related to Server: InnoDB Plugin.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| MySQL | >=5.6.0<=5.6.30 | |
| MySQL | >=5.7.0<=5.7.12 |
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-8288?
The severity of CVE-2016-8288 is identified as medium, affecting the integrity of Oracle MySQL.
How do I fix CVE-2016-8288?
To fix CVE-2016-8288, upgrade to MySQL version 5.6.31 or higher, or 5.7.13 or higher.
Who is affected by CVE-2016-8288?
CVE-2016-8288 affects remote authenticated users of Oracle MySQL version 5.6.30 and earlier, and 5.7.12 and earlier.
What types of attacks are possible with CVE-2016-8288?
CVE-2016-8288 may allow remote authenticated users to manipulate data integrity in MySQL.
When was CVE-2016-8288 disclosed?
CVE-2016-8288 was disclosed in October 2016 as part of Oracle's security advisory.
- agent/type
- agent/remedy
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/description
- agent/first-publish-date
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/softwarecombine
- vendor/oracle
- canonical/mysql
- version/mysql/5.6.0
- version/mysql/5.6.30
- version/mysql/5.7.0
- version/mysql/5.7.12