dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-2760

MEDIUM · 5.5 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 10.2.32 / 10.3.23 or later.
See remediation →
61/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 Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 5.7.29 and prior and 8.0.19 and prior. 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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.0 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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 Server's InnoDB storage engine allowing high-privileged attackers with network access to cause a denial of service (hang or crash) or perform unauthorized insert, update, or delete operations on accessible data.

MitigationApply Oracle's April 2020 Critical Patch Update to upgrade MySQL Server to version 5.7.30 or 8.0.20 or later, which contains the fix for this InnoDB vulnerability.

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.7.0, <= 5.7.29>= 8.0.0, <= 8.0.19
FedoraOperating system
Affected:= 30= 31= 32
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.10= 20.04
MariaDBDatabase / datastore
Affected:>= 10.2.0, < 10.2.32>= 10.3.0, < 10.3.23>= 10.4.0, < 10.4.13
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

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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/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 installed MySQL or MariaDB version
    Run `mysql --version` or `mariadb --version` from command line, or query `SELECT VERSION();` while connected to the database
    Affected if Version is Oracle MySQL 5.7.0 through 5.7.29, or 8.0.0 through 8.0.19, or MariaDB 10.2.0 through 10.2.31, 10.3.0 through 10.3.22, or 10.4.0 through 10.4.12
  2. Confirm InnoDB storage engine is in use
    Query `SHOW ENGINES;` and check that InnoDB shows 'YES' in the Support column, or check `SHOW VARIABLES LIKE 'default_storage_engine';`
    Affected if InnoDB is enabled as the default or as an available storage engine (this is the default in affected versions)
  3. Verify network exposure of MySQL service
    Check if the MySQL/MariaDB port (default 3306) is listening on a network interface accessible to untrusted users. Use `netstat -tlnp | grep 3306` or `ss -tlnp | grep 3306`
    Affected if MySQL is bound to a non-localhost interface (0.0.0.0 or any IP other than 127.0.0.1)
  4. For NetApp products, check Active Iq Unified Manager version
    Locate the installed NetApp product version through the application web interface or `rpm -q` / `dpkg -q` package queries
    Affected if NetApp Active Iq Unified Manager version is 7.x or 9.5.x through 9.9.x (all versions listed are affected)

Your environment is affected if you run Oracle MySQL 5.7.x up to 29, 8.0.x up to 19, or MariaDB 10.2.x/10.3.x/10.4.x below the fixed versions, with InnoDB enabled and network-accessible high-privileged accounts.

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 10.2.32 / 10.3.23 / 10.4.13 or later
Fixed in 10.2.3210.3.2310.4.13
Interim mitigation

Apply Oracle's April 2020 Critical Patch Update to upgrade MySQL Server to version 5.7.30 or 8.0.20 or later, which contains the fix for this InnoDB vulnerability.

Fix this in MySQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2760 — 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-2760 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