CVE-2020-2570: Medium severity ORACLE MySQL vulnerability

Published Jan 15, 2020
·
Updated

A vulnerability was found in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are affected are 5.7.28 and prior and 8.0.18 and prior. Difficult to exploit vulnerability allows unauthenticated 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.

Reference: https://www.oracle.com/security-alerts/cpujan2020.html

Other sources

Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are affected are 5.7.28 and prior and 8.0.18 and prior. Difficult to exploit vulnerability allows unauthenticated 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.0 Base Score 5.9 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H).

Launchpad

Affected Software

8 affected componentsFixes available
debian/mysql-5.7
redhat/mysql<5.7.29
5.7.29
redhat/mysql<8.0.19
8.0.19
ORACLE MySQL>=5.7.0<=5.7.28
ORACLE MySQL>=8.0.0<=8.0.18
Canonical Ubuntu Linux=16.04
Canonical Ubuntu Linux=18.04
Canonical Ubuntu Linux=19.10

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/mysql to a version that resolves this vulnerability.

    Fixed in 5.7.29
  2. Upgrade

    Upgrade redhat/mysql to a version that resolves this vulnerability.

    Fixed in 8.0.19
  3. Upgrade

    Upgrade Oracle MySQL MySQL Client (C API) to a version that resolves this vulnerability.

    Fixed in 8.0.18
  4. Upgrade

    Upgrade Oracle MySQL MySQL Client (C API) to a version that resolves this vulnerability.

    Fixed in 5.7.28

Event History

Jan 15, 2020
CVE Published
via MITRE·04:34 PM
Data Sourced
via MITRE·04:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:46 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·02:26 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2020-2570?

CVE-2020-2570 has been classified as a difficult to exploit vulnerability affecting specific versions of MySQL.

2

How do I fix CVE-2020-2570?

To address CVE-2020-2570, upgrade MySQL to version 5.7.29 or 8.0.19 or later.

3

Which MySQL versions are affected by CVE-2020-2570?

CVE-2020-2570 affects MySQL versions 5.7.28 and prior and 8.0.18 and prior.

4

Who can exploit CVE-2020-2570?

CVE-2020-2570 can be exploited by unauthenticated attackers with network access.

5

What protocols are involved in CVE-2020-2570 exploitation?

CVE-2020-2570 can be compromised via multiple network protocols.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203