dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21600

HIGH · 7.2 CVSS v3.1 Published 2022-10-18
Fix available
A fix is available. Upgrade to after 8.0.27 or later.
See remediation →
78/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 high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in takeover of MySQL Server. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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

A vulnerability in the MySQL Server Optimizer component allows a high-privileged attacker with network access to compromise the MySQL Server and potentially take it over. The attack has low complexity and requires high privileges (PR:H), but can achieve full confidentiality, integrity, and availability impacts.

MitigationApply the latest MySQL 8.0 security updates (8.0.28 or later) to address this vulnerability. Ensure high-privileged accounts are limited and network access is restricted to only necessary protocols and sources.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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. Check MySQL Server version
    Run `SELECT VERSION();` or check the MySQL server package version using `mysql --version` or your system's package manager (e.g., `rpm -qa | grep mysql-server` or `dpkg -l | grep mysql-server`)
    Affected if The version is greater than or equal to 8.0.0 and less than or equal to 8.0.27
  2. Check if MySQL Optimizer component is in use
    Verify the MySQL Server is running and accessible. The vulnerability exists in the Optimizer component, which is a core part of MySQL Server - no specific feature flag needs to be enabled for the flaw to apply to a running MySQL instance
    Affected if MySQL Server 8.0.x is running in the affected version range
  3. Check for NetApp Oncommand Insight installation
    Inspect the system for installed NetApp Oncommand Insight software using system inventory tools or by checking for typical installation directories (e.g., looking for OCI installation paths or services)
    Affected if NetApp Oncommand Insight is installed on the system (all versions are affected)
  4. Check for NetApp Oncommand Workflow Automation installation
    Inspect the system for installed NetApp Oncommand Workflow Automation software using system inventory tools or by checking for typical installation directories (e.g., looking for OWA installation paths or services)
    Affected if NetApp Oncommand Workflow Automation is installed on the system (all versions are affected)

You are affected if you are running Oracle MySQL version 8.0.0 through 8.0.27, or if you have NetApp Oncommand Insight or NetApp Oncommand Workflow Automation installed on your system.

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 latest MySQL 8.0 security updates (8.0.28 or later) to address this vulnerability. Ensure high-privileged accounts are limited and network access is restricted to only necessary protocols and sources.

Recommended fix Moderate confidence

MySQL 8.0.28 or later (or appropriate NetApp-supported patch for Oncommand products)

  1. 1. Back up your MySQL database before performing any upgrade
  2. 2. Review MySQL 8.0.28 release notes for any additional changes that may affect your applications
  3. 3. Test the upgrade in a non-production environment first
  4. 4. Perform the upgrade to MySQL 8.0.28 or later following Oracle's standard upgrade procedures
  5. 5. Verify that all applications and connections work correctly after the upgrade
  6. 6. For NetApp Oncommand Insight and Oncommand Workflow Automation, contact NetApp support for product-specific patches if direct MySQL upgrades are not feasible
Caveat MySQL minor version upgrades typically have minimal breaking changes, but review release notes for optimizer changes that may affect query execution plans

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-21600 — 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-21600 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