CVE-2017-10320: Medium severity mysql vulnerability
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: InnoDB). Supported versions that are affected are 5.7.19 and earlier. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.
External References:
http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html#AppendixMSQL
Other sources
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: InnoDB). Supported versions that are affected are 5.7.19 and earlier. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.0 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2017-10320?
CVE-2017-10320 is considered an easily exploitable vulnerability that allows high privileged attackers to compromise MySQL Server.
How do I fix CVE-2017-10320?
To fix CVE-2017-10320, upgrade to MySQL version 5.7.20 or later, or to MariaDB version 10.2.8 or later.
Which MySQL versions are affected by CVE-2017-10320?
Versions 5.7.19 and earlier of MySQL are affected by CVE-2017-10320.
Can CVE-2017-10320 be exploited remotely?
Yes, CVE-2017-10320 can be easily exploited by attackers with network access through multiple protocols.
What component of Oracle MySQL is affected by CVE-2017-10320?
CVE-2017-10320 affects the MySQL Server component, specifically the InnoDB subcomponent.