dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21352

MEDIUM · 5.9 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.26 or later.
See remediation →
65/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.26 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 creation, deletion or modification access to critical data or all MySQL Server accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.9 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/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

CVE-2022-21352 is a vulnerability in the InnoDB storage engine of MySQL Server. The flaw allows a high-privileged attacker with network access to potentially modify or delete critical data, or cause a denial of service by hanging or crashing the MySQL Server. It is difficult to exploit due to high attack complexity and requires high privileges.

MitigationApply the Oracle Critical Patch Update (January 2022) or subsequent patch that addresses this vulnerability in MySQL 8.0.26 and prior versions. Upgrade to a patched MySQL version and restrict high-privileged access 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.26
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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/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 version
    Run command: SELECT VERSION(); or mysqld --version
    Affected if Version is between 8.0.0 and 8.0.26 inclusive (e.g., 8.0.25, 8.0.20, 8.0.5)
  2. Confirm InnoDB storage engine is in use
    Run query: SHOW ENGINES; Look for InnoDB with 'YES' in the Support column
    Affected if InnoDB engine is enabled (this is the default storage engine in MySQL 8.0)
  3. Verify MySQL is listening on network interfaces
    Check configuration: SHOW VARIABLES LIKE 'bind_address'; Review network exposure with netstat -tlnp | grep 3306
    Affected if Bind address is not 127.0.0.1 or localhost (vulnerable if accessible over network)
  4. Check NetApp Oncommand Insight version
    Log into the Oncommand Insight web interface or check installed version via: docker ps (if containerized) or application version panel
    Affected if Any version is installed (all versions are affected per advisory)
  5. Check NetApp Oncommand Workflow Automation version
    Log into the Oncommand Workflow Automation interface or check version via administration console
    Affected if Any version is installed (all versions are affected per advisory)

You are affected if running MySQL 8.0.0-8.0.26 with InnoDB enabled and network exposure, or if using any version of NetApp Oncommand Insight or Oncommand Workflow Automation.

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.26
Interim mitigation

Apply the Oracle Critical Patch Update (January 2022) or subsequent patch that addresses this vulnerability in MySQL 8.0.26 and prior versions. Upgrade to a patched MySQL version and restrict high-privileged access to trusted personnel only.

Recommended fix Moderate confidence

MySQL 8.0.27 or later (preferably latest 8.0.x)

  1. 1. Back up all MySQL databases before upgrading
  2. 2. Stop the MySQL Server service
  3. 3. Upgrade MySQL Server from 8.0.26 or earlier to version 8.0.27 or later (recommended: latest 8.0.x LTS release)
  4. 4. Run mysql_upgrade to check and repair tables if needed
  5. 5. Restart the MySQL Server service
  6. 6. Verify the InnoDB version and MySQL version after upgrade using: SELECT VERSION();
  7. 7. For NetApp Oncommand Insight and Oncommand Workflow Automation: check NetApp's security advisories (security.netapp.com) for product-specific patches - these products have no fix listed in this CVE and require vendor-provided patches
Caveat Oracle major version upgrades typically maintain backward compatibility but always test in staging first; check release notes for deprecated features between 8.0.0-8.0.26 and your target version

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

Fix this in MySQL Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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