What is the severity of CVE-2016-0659?

CVE-2016-0659 has a medium severity rating due to its potential impact on the availability of the MySQL database.

How do I fix CVE-2016-0659?

To fix CVE-2016-0659, users should upgrade their Oracle MySQL installations to version 5.7.12 or later.

Who is affected by CVE-2016-0659?

CVE-2016-0659 affects local users running Oracle MySQL versions up to and including 5.7.11.

What kind of attack vector is associated with CVE-2016-0659?

CVE-2016-0659 is associated with an unspecified vulnerability in the Optimizer related to local user actions.

Is there a workaround for CVE-2016-0659?

There are no known workarounds for CVE-2016-0659, making upgrading the software the best solution.

Vulnerability/
CVE-2016-0659

medium

5.5

21/4/2016

15/10/2024

CVE-2016-0659

First published: Thu Apr 21 2016(Updated: )

Unspecified vulnerability in Oracle MySQL 5.7.11 and earlier allows local users to affect availability via vectors related to Optimizer.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	<=5.7.11

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuapr2016v3-2985753.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-0659?
CVE-2016-0659 has a medium severity rating due to its potential impact on the availability of the MySQL database.
How do I fix CVE-2016-0659?
To fix CVE-2016-0659, users should upgrade their Oracle MySQL installations to version 5.7.12 or later.
Who is affected by CVE-2016-0659?
CVE-2016-0659 affects local users running Oracle MySQL versions up to and including 5.7.11.
What kind of attack vector is associated with CVE-2016-0659?
CVE-2016-0659 is associated with an unspecified vulnerability in the Optimizer related to local user actions.
Is there a workaround for CVE-2016-0659?
There are no known workarounds for CVE-2016-0659, making upgrading the software the best solution.

agent/type
agent/softwarecombine
agent/severity
agent/author
agent/references
agent/remedy
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
vendor/oracle
canonical/mysql
version/mysql/5.7.11

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-0659?
CVE-2016-0659 has a medium severity rating due to its potential impact on the availability of the MySQL database.
How do I fix CVE-2016-0659?
To fix CVE-2016-0659, users should upgrade their Oracle MySQL installations to version 5.7.12 or later.
Who is affected by CVE-2016-0659?
CVE-2016-0659 affects local users running Oracle MySQL versions up to and including 5.7.11.
What kind of attack vector is associated with CVE-2016-0659?
CVE-2016-0659 is associated with an unspecified vulnerability in the Optimizer related to local user actions.
Is there a workaround for CVE-2016-0659?
There are no known workarounds for CVE-2016-0659, making upgrading the software the best solution.