dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2021-2048

MEDIUM · 5.0 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 8.0.22 or later.
See remediation →
56/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 8.0.22 and prior. Difficult to exploit 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.1 Base Score 5.0 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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 (versions 8.0.22 and prior). A high-privileged attacker with network access can cause a denial of service (hang or crash) or gain unauthorized DML access (insert/update/delete) to some MySQL data. The difficulty rating is 'difficult to exploit' and requires high privileges.

MitigationUpgrade MySQL Server to version 8.0.23 or later. Alternatively, restrict network access to MySQL and limit privileged accounts to trusted personnel only.

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:>= 8.0.0, <= 8.0.22
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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:H/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 MySQL Server version
    Run command: mysql --version or log into MySQL and execute SELECT VERSION();
    Affected if Version is between 8.0.0 and 8.0.22 inclusive (verify using mysql --version or SELECT VERSION())
  2. Confirm InnoDB storage engine is in use
    Execute query: SHOW ENGINES; and check if InnoDB is listed as ENABLED or DEFAULT
    Affected if InnoDB engine is enabled (it is the default storage engine in MySQL 8.0, so most installations are affected if version check passes)
  3. Check MySQL network bind address
    Check MySQL configuration file (my.cnf or my.ini) for bind-address setting, or query: SHOW VARIABLES LIKE 'bind_address';
    Affected if bind-address is set to 0.0.0.0 or an accessible IP, making MySQL network-accessible
  4. Verify privilege level of MySQL accounts
    Query: SELECT user, host, plugin FROM mysql.user; to identify accounts and their authentication methods
    Affected if Multiple high-privileged accounts exist beyond those strictly required (privilege level matters for exploit feasibility)
  5. Detect NetApp Oncommand Insight installation
    Check system for installed software named 'Oncommand Insight' or review NetApp product documentation
    Affected if Oncommand Insight is installed (all versions are affected)
  6. Detect NetApp Oncommand Workflow Automation or SnapCenter
    Check system for installed software named 'Oncommand Workflow Automation' or 'SnapCenter'
    Affected if Either Oncommand Workflow Automation or SnapCenter is installed (all versions are affected)

You are affected if you run MySQL Server version 8.0.0 through 8.0.22 with InnoDB enabled and network accessibility, or if you have any NetApp Oncommand Insight, Oncommand Workflow Automation, or SnapCenter installed.

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 a release after 8.0.22
Interim mitigation

Upgrade MySQL Server to version 8.0.23 or later. Alternatively, restrict network access to MySQL and limit privileged accounts to trusted personnel only.

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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