dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2021-2011

MEDIUM · 5.9 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to 5.5.61 / 10.0.35 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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.7.32 and prior and 8.0.22 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.1 Base Score 5.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/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

Denial of service vulnerability in MySQL Client C API. Unauthenticated remote attackers with network access can cause MySQL clients to hang or crash repeatedly. The vulnerability affects MySQL Client versions 5.7.32 and prior, and 8.0.22 and prior, and is described as difficult to exploit.

MitigationUpgrade MySQL Client to a version beyond 5.7.32 and 8.0.22. Since this is a client-side vulnerability, ensure all systems running MySQL client utilities are identified and patched.

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.32>= 8.0.0, <= 8.0.22
FedoraOperating system
Affected:= 32= 33
MariaDBDatabase / datastore
Affected:>= 5.5.0, < 5.5.61>= 10.0.0, < 10.0.35>= 10.1.0, < 10.1.33>= 10.2.0, < 10.2.15
Active Iq Unified ManagerApplication
Affected:all versions
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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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. Check MySQL client version
    Run `mysql --version` or `mysql -V` to display the installed MySQL client version. On RPM-based systems also check with `rpm -q mysql` or `rpm -qa | grep mysql`. On Debian-based systems check with `dpkg -l | grep mysql`.
    Affected if The version displayed is 5.7.32 or prior, or 8.0.22 or prior (for example 5.7.32, 8.0.22, 5.7.31, 8.0.21, etc.)
  2. Check MariaDB client version
    Run `mariadb --version` or `mysql --version` (MariaDB binaries may be named mysql). On RPM systems check `rpm -q mariadb`. On Debian systems check `dpkg -l | grep mariadb`.
    Affected if The version displayed falls within these ranges: 5.5.0 to 5.5.60, 10.0.0 to 10.0.34, 10.1.0 to 10.1.32, or 10.2.0 to 10.2.14.
  3. Identify client machines with MySQL utilities
    Audit all systems on the network for installed MySQL or MariaDB client packages. Search for binaries including mysql, mysqldump, mysqlpump, mysqlbinlog, and mariadb equivalent tools. Use asset inventory or package management tools to list installed database client packages.
    Affected if Any system has a MySQL or MariaDB client package installed with a version matching the affected ranges from steps 1 or 2.
  4. Check NetApp product installations
    On systems running NetApp Active IQ Unified Manager, Oncommand Insight, or Oncommand Workflow Automation, check the installed product version or bundle version using the product's version command or web interface.
    Affected if Any NetApp product listed is installed (all versions of these products are affected per the advisory).

You are affected if any system in your environment runs a MySQL client version 5.7.32 or prior, 8.0.22 or prior, or any MariaDB client version within the affected ranges, or any of the NetApp products listed, and those clients can connect to network-accessible MySQL 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.61 / 10.0.35 / 10.1.33 or later
Fixed in 5.5.6110.0.3510.1.33
Interim mitigation

Upgrade MySQL Client to a version beyond 5.7.32 and 8.0.22. Since this is a client-side vulnerability, ensure all systems running MySQL client utilities are identified and patched.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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