What is the severity of CVE-2016-0663?

CVE-2016-0663 is rated as a moderate severity vulnerability.

How do I fix CVE-2016-0663?

To fix CVE-2016-0663, you should upgrade to MySQL version 5.7.11 or later.

What type of vulnerability is CVE-2016-0663?

CVE-2016-0663 is an unspecified vulnerability affecting the Performance Schema in Oracle MySQL.

Who is affected by CVE-2016-0663?

Local users of Oracle MySQL version 5.7.10 and earlier are affected by CVE-2016-0663.

Is there a workaround for CVE-2016-0663?

There is no official workaround for CVE-2016-0663; upgrading is the recommended mitigation.

Vulnerability/
CVE-2016-0663

medium

4.7

21/4/2016

15/10/2024

CVE-2016-0663

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 Performance Schema.

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-0663?
CVE-2016-0663 is rated as a moderate severity vulnerability.
How do I fix CVE-2016-0663?
To fix CVE-2016-0663, you should upgrade to MySQL version 5.7.11 or later.
What type of vulnerability is CVE-2016-0663?
CVE-2016-0663 is an unspecified vulnerability affecting the Performance Schema in Oracle MySQL.
Who is affected by CVE-2016-0663?
Local users of Oracle MySQL version 5.7.10 and earlier are affected by CVE-2016-0663.
Is there a workaround for CVE-2016-0663?
There is no official workaround for CVE-2016-0663; upgrading is the recommended mitigation.

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-0663?
CVE-2016-0663 is rated as a moderate severity vulnerability.
How do I fix CVE-2016-0663?
To fix CVE-2016-0663, you should upgrade to MySQL version 5.7.11 or later.
What type of vulnerability is CVE-2016-0663?
CVE-2016-0663 is an unspecified vulnerability affecting the Performance Schema in Oracle MySQL.
Who is affected by CVE-2016-0663?
Local users of Oracle MySQL version 5.7.10 and earlier are affected by CVE-2016-0663.
Is there a workaround for CVE-2016-0663?
There is no official workaround for CVE-2016-0663; upgrading is the recommended mitigation.