What is the severity of CVE-2016-0654?

CVE-2016-0654 has not been assigned a Common Vulnerability Scoring System (CVSS) score, but it is classified as a local availability vulnerability.

How do I fix CVE-2016-0654?

To mitigate CVE-2016-0654, upgrade to MySQL version 5.7.11 or later, where the vulnerability has been addressed.

What software versions are affected by CVE-2016-0654?

CVE-2016-0654 affects Oracle MySQL versions 5.7.10 and earlier.

Are there any known exploits for CVE-2016-0654?

As of now, there are no public exploits documented for CVE-2016-0654.

Who is impacted by CVE-2016-0654?

Local users of affected versions of Oracle MySQL are impacted by CVE-2016-0654.

Vulnerability/
CVE-2016-0654

medium

5.5

21/4/2016

15/10/2024

CVE-2016-0654

First published: Thu Apr 21 2016(Updated: )

Unspecified vulnerability in Oracle MySQL 5.7.10 and earlier allows local users to affect availability via vectors related to InnoDB, a different vulnerability than CVE-2016-0656.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	<=5.7.10

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-0654?
CVE-2016-0654 has not been assigned a Common Vulnerability Scoring System (CVSS) score, but it is classified as a local availability vulnerability.
How do I fix CVE-2016-0654?
To mitigate CVE-2016-0654, upgrade to MySQL version 5.7.11 or later, where the vulnerability has been addressed.
What software versions are affected by CVE-2016-0654?
CVE-2016-0654 affects Oracle MySQL versions 5.7.10 and earlier.
Are there any known exploits for CVE-2016-0654?
As of now, there are no public exploits documented for CVE-2016-0654.
Who is impacted by CVE-2016-0654?
Local users of affected versions of Oracle MySQL are impacted by CVE-2016-0654.

agent/references
agent/type
agent/softwarecombine
agent/severity
agent/author
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.10

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-0654?
CVE-2016-0654 has not been assigned a Common Vulnerability Scoring System (CVSS) score, but it is classified as a local availability vulnerability.
How do I fix CVE-2016-0654?
To mitigate CVE-2016-0654, upgrade to MySQL version 5.7.11 or later, where the vulnerability has been addressed.
What software versions are affected by CVE-2016-0654?
CVE-2016-0654 affects Oracle MySQL versions 5.7.10 and earlier.
Are there any known exploits for CVE-2016-0654?
As of now, there are no public exploits documented for CVE-2016-0654.
Who is impacted by CVE-2016-0654?
Local users of affected versions of Oracle MySQL are impacted by CVE-2016-0654.