dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21302

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.27 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 Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows low 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. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/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 · moderate confidence

This is a denial-of-service vulnerability in the InnoDB storage engine of MySQL Server 8.0.27 and prior versions. A low-privileged attacker with network access can exploit this difficult-to-exploit flaw to cause MySQL Server to hang or crash repeatedly, resulting in complete availability loss.

MitigationUpgrade MySQL Server to a version higher than 8.0.27 that includes the security patch for this vulnerability. In the interim, restrict network access to MySQL servers and follow the principle of least privilege for database user accounts.

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.27
FedoraOperating system
Affected:= 34= 35
Active Iq Unified ManagerApplication
Affected:all versions
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 Server version
    Run `mysql --version` from command line, or execute `SELECT VERSION();` within a MySQL client session
    Affected if Version is 8.0.0 through 8.0.27 inclusive
  2. Confirm InnoDB storage engine is active
    Execute `SHOW ENGINES;` in MySQL and verify InnoDB shows 'YES' in the Support column, or run `SHOW VARIABLES LIKE 'innodb_version';`
    Affected if InnoDB engine is enabled (default configuration)
  3. Check MySQL network binding
    Review MySQL configuration files (my.cnf or my.ini) for 'bind-address' setting, or run `SHOW VARIABLES LIKE 'bind_address';` to determine if MySQL listens on network interfaces
    Affected if MySQL is bound to a network-accessible IP address rather than localhost only

You are affected if MySQL Server version is between 8.0.0 and 8.0.27, InnoDB storage engine is active, and the database is reachable over the network.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.27
Interim mitigation

Upgrade MySQL Server to a version higher than 8.0.27 that includes the security patch for this vulnerability. In the interim, restrict network access to MySQL servers and follow the principle of least privilege for database user accounts.

Recommended fix High confidence

MySQL 8.0.28 or later

  1. 1. Back up all MySQL databases using mysqldump or mariadb-dump
  2. 2. Stop the MySQL service: sudo systemctl stop mysql or sudo systemctl stop mysqld
  3. 3. Update the MySQL repository or package manager
  4. 4. Upgrade MySQL server: sudo dnf update mysql-server (Fedora) or use appropriate package manager for your system
  5. 5. Start the MySQL service: sudo systemctl start mysql
  6. 6. Run mysql_upgrade to check and migrate databases if needed
  7. 7. Verify MySQL version is 8.0.28 or later: mysql -V
Caveat Point releases within 8.0.x are typically backward-compatible; review Oracle MySQL 8.0.28 release notes for any minor behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

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-2022-21302 — 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-2022-21302 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