dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21351

HIGH · 7.1 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.27 or later.
See remediation →
77/100
Remediation priority · High
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: Server: Optimizer). Supported versions that are affected are 8.0.27 and prior. Easily exploitable 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 as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 7.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 the MySQL Server Optimizer component affecting versions 8.0.27 and prior. Easily exploitable by low-privileged attackers with network access, allowing denial of service (hang or crash) and unauthorized data modification (insert/update/delete) to some accessible data.

MitigationApply the Oracle Critical Patch Update that addresses this vulnerability, typically by upgrading to a patched MySQL Server version. Restrict network access to MySQL servers as an interim measure.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check MySQL Server version
    Run 'SELECT VERSION();' in MySQL client or execute 'mysqld --version' from command line
    Affected if Version is 8.0.0 through 8.0.27 inclusive (e.g., 8.0.27, 8.0.15, 8.0.5)
  2. Check for NetApp Oncommand Insight installation
    Identify if Oncommand Insight software is installed on the system (check installed programs, documentation, or contact NetApp support)
    Affected if Oncommand Insight is present on the system (all versions are affected)
  3. Check for NetApp Oncommand Workflow Automation installation
    Identify if Oncommand Workflow Automation software is installed on the system (check installed programs, documentation, or contact NetApp support)
    Affected if Oncommand Workflow Automation is present on the system (all versions are affected)
  4. Confirm Optimizer component is in use
    The MySQL Optimizer is a core component active for all queries; verify MySQL Server is actively running queries
    Affected if MySQL Server 8.0.x is running queries (the Optimizer handles query execution planning for all queries)

You are affected if running MySQL Server versions 8.0.0 through 8.0.27, OR if NetApp Oncommand Insight or Oncommand Workflow Automation is installed (all versions).

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

Apply the Oracle Critical Patch Update that addresses this vulnerability, typically by upgrading to a patched MySQL Server version. Restrict network access to MySQL servers as an interim measure.

Recommended fix High confidence

MySQL 8.0.28 or later (8.0.x series)

  1. 1. Back up all MySQL databases before performing the upgrade
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Upgrade MySQL Server from version 8.0.0-8.0.27 to version 8.0.28 or later
  4. 4. After upgrade, verify MySQL service is running and databases are accessible
  5. 5. Test application connectivity and functionality
Caveat Minor point releases in 8.0.x typically have low risk; review Oracle MySQL 8.0.28 release notes for any optimizer-specific changes or known issues before upgrading

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

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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