What is the severity of CVE-2016-5627?

CVE-2016-5627 is classified as a medium severity vulnerability affecting Oracle MySQL.

How do I fix CVE-2016-5627?

To fix CVE-2016-5627, upgrade to MySQL version 5.6.32 or higher, or 5.7.14 or higher.

Who is affected by CVE-2016-5627?

CVE-2016-5627 affects remote authenticated users of Oracle MySQL versions 5.6.31 and earlier, and 5.7.13 and earlier.

What components of Oracle MySQL are impacted by CVE-2016-5627?

CVE-2016-5627 impacts the InnoDB storage engine component of Oracle MySQL.

Can CVE-2016-5627 lead to a denial of service?

Yes, CVE-2016-5627 can affect the availability of the MySQL server, potentially leading to a denial of service.

Vulnerability/
CVE-2016-5627

medium

6.5

25/10/2016

10/10/2024

CVE-2016-5627

First published: Tue Oct 25 2016(Updated: )

Unspecified vulnerability in Oracle MySQL 5.6.31 and earlier and 5.7.13 and earlier allows remote authenticated users to affect availability via vectors related to Server: InnoDB.

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
MySQL	>=5.6.0<=5.6.31
MySQL	>=5.7.0<=5.7.13

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-5627?
CVE-2016-5627 is classified as a medium severity vulnerability affecting Oracle MySQL.
How do I fix CVE-2016-5627?
To fix CVE-2016-5627, upgrade to MySQL version 5.6.32 or higher, or 5.7.14 or higher.
Who is affected by CVE-2016-5627?
CVE-2016-5627 affects remote authenticated users of Oracle MySQL versions 5.6.31 and earlier, and 5.7.13 and earlier.
What components of Oracle MySQL are impacted by CVE-2016-5627?
CVE-2016-5627 impacts the InnoDB storage engine component of Oracle MySQL.
Can CVE-2016-5627 lead to a denial of service?
Yes, CVE-2016-5627 can affect the availability of the MySQL server, potentially leading to a denial of service.

agent/type
agent/remedy
agent/severity
agent/author
agent/references
agent/description
agent/event
agent/first-publish-date
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.31
version/mysql/5.7.0
version/mysql/5.7.13

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-5627?
CVE-2016-5627 is classified as a medium severity vulnerability affecting Oracle MySQL.
How do I fix CVE-2016-5627?
To fix CVE-2016-5627, upgrade to MySQL version 5.6.32 or higher, or 5.7.14 or higher.
Who is affected by CVE-2016-5627?
CVE-2016-5627 affects remote authenticated users of Oracle MySQL versions 5.6.31 and earlier, and 5.7.13 and earlier.
What components of Oracle MySQL are impacted by CVE-2016-5627?
CVE-2016-5627 impacts the InnoDB storage engine component of Oracle MySQL.
Can CVE-2016-5627 lead to a denial of service?
Yes, CVE-2016-5627 can affect the availability of the MySQL server, potentially leading to a denial of service.