CVE-2017-3641: Medium severity mysql vulnerability
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DML). Supported versions that are affected are 5.5.56 and earlier, 5.6.36 and earlier and 5.7.18 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/cpujul2017-3236622.html#AppendixMSQL
Other sources
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: DML). Supported versions that are affected are 5.5.56 and earlier, 5.6.36 and earlier and 5.7.18 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).
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2017-3641?
CVE-2017-3641 is classified as an easily exploitable vulnerability that allows high privileged attackers with network access.
How do I fix CVE-2017-3641?
To mitigate CVE-2017-3641, upgrade MySQL to version 5.5.57, 5.6.37, or 5.7.19, or use the corresponding fixed version of MariaDB.
What versions of MySQL are affected by CVE-2017-3641?
CVE-2017-3641 affects MySQL versions 5.5.56 and earlier, 5.6.36 and earlier, and 5.7.18 and earlier.
What is the impact of CVE-2017-3641 on MySQL Server?
CVE-2017-3641 allows attackers to execute unauthorized actions on the MySQL Server, potentially compromising the integrity and confidentiality of data.
Is there any workaround for CVE-2017-3641?
There are no specific workarounds provided for CVE-2017-3641, and the recommended solution is to apply the security updates.