CVE-2020-14550: Medium severity Oracle MySQL vulnerability
Last updated 24 July 2024
Other sources
Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are affected are 5.6.48 and prior, 5.7.30 and prior and 8.0.20 and prior. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Client.
External References:
https://www.oracle.com/security-alerts/cpujul2020.html#AppendixMSQL
— Red Hat
Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are affected are 5.6.48 and prior, 5.7.30 and prior and 8.0.20 and prior. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Client. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
— Launchpad
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2020-14550?
CVE-2020-14550 is rated as a low severity vulnerability that is difficult to exploit.
How do I fix CVE-2020-14550?
To fix CVE-2020-14550, update your MySQL Client product to version 5.6.49, 5.7.31, or 8.0.21.
Which versions of MySQL are affected by CVE-2020-14550?
CVE-2020-14550 affects MySQL versions 5.6.48 and prior, 5.7.30 and prior, and 8.0.20 and prior.
Can MariaDB be affected by CVE-2020-14550?
Yes, certain versions of MariaDB such as 5.5.61, 10.0.35, 10.1.33, and 10.2.15 are also affected by CVE-2020-14550.
Is it safe to use MySQL after addressing CVE-2020-14550?
Once you update to a non-vulnerable version, using MySQL is considered safe regarding CVE-2020-14550.