CVE-2016-3440
First published: Thu Jul 21 2016(Updated: )
Unspecified vulnerability in Oracle MySQL 5.7.11 and earlier allows remote authenticated users to affect availability via vectors related to Server: Optimizer.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle MySQL Installer | <=5.7.11 |
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-3440?
CVE-2016-3440 has a medium severity rating due to its impact on availability.
How do I fix CVE-2016-3440?
To fix CVE-2016-3440, update your Oracle MySQL to version 5.7.12 or later.
Who is affected by CVE-2016-3440?
CVE-2016-3440 affects remote authenticated users of Oracle MySQL versions 5.7.11 and earlier.
What types of attacks could exploit CVE-2016-3440?
CVE-2016-3440 could be exploited to disrupt the availability of the MySQL server.
Is there a workaround for CVE-2016-3440?
There are no official workarounds for CVE-2016-3440; updating MySQL is the recommended action.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/author
- agent/remedy
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/oracle
- canonical/oracle mysql
- version/oracle mysql/5.7.11