dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-2752

MEDIUM · 5.3 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 5.5.68 / 10.1.45 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are affected are 5.6.47 and prior, 5.7.27 and prior and 8.0.17 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.0 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Vulnerability in MySQL Client C API allows low-privileged remote attackers to cause denial of service via crashing or hanging the client application. The attack requires network access and has high attack complexity, making it difficult but not impossible to exploit.

MitigationUpdate MySQL Client to versions beyond 8.0.17, 5.7.27, or 5.6.47 as appropriate. If immediate patching is not feasible, restrict network access to trusted servers and monitor for unusual client behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:>= 5.6.0, <= 5.6.47>= 5.7.0, <= 5.7.27>= 8.0.0, <= 8.0.17
MariaDBDatabase / datastore
Affected:>= 5.5.0, < 5.5.68>= 10.1.0, < 10.1.45>= 10.2.0, < 10.2.32>= 10.3.0, < 10.3.23>= 10.4.0, < 10.4.13
FedoraOperating system
Affected:= 31= 32
LeapOperating system
Affected:= 15.1
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
Oncommand InsightApplication
Affected:all versions
Oncommand Workflow AutomationApplication
Affected:all versions
SnapcenterApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MySQL client version
    Run 'mysql --version' or check the installed package with your system package manager (e.g., 'rpm -q mysql' or 'dpkg -l mysql-client')
    Affected if The version is >= 5.6.0 and <= 5.6.47, OR >= 5.7.0 and <= 5.7.27, OR >= 8.0.0 and <= 8.0.17
  2. Identify MariaDB client version
    Run 'mariadb --version' or check the installed package with your system package manager (e.g., 'rpm -q mariadb' or 'dpkg -l mariadb-client')
    Affected if The version is >= 5.5.0 and < 5.5.68, OR >= 10.1.0 and < 10.1.45, OR >= 10.2.0 and < 10.2.32, OR >= 10.3.0 and < 10.3.23, OR >= 10.4.0 and < 10.4.13
  3. Check if MySQL or MariaDB client libraries are in use
    For compiled applications using the client library, check the library version via 'ldd' on the executable or inspect the shared library file directly
    Affected if The linked libmysqlclient or libmariadb library version falls within the affected version ranges
  4. Verify NetApp product installations
    Check installed versions of NetApp Active IQ Unified Manager, Oncommand Insight, Oncommand Workflow Automation, or Snapcenter using each product's version command or documentation
    Affected if The product is any version of Oncommand Insight, Oncommand Workflow Automation, or Snapcenter; or Active IQ Unified Manager versions >= 7.3 or >= 9.5; or the specific product version is within the MySQL client vulnerable ranges

Your environment is affected if you run any MySQL client (mysql CLI or library), MariaDB client, or affected NetApp product versions AND the client has network access to connect to remote servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 5.5.68 / 10.1.45 / 10.2.32 or later
Fixed in 5.5.6810.1.4510.2.32
Interim mitigation

Update MySQL Client to versions beyond 8.0.17, 5.7.27, or 5.6.47 as appropriate. If immediate patching is not feasible, restrict network access to trusted servers and monitor for unusual client behavior.

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2752 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2752 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data