dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21322

MEDIUM · 6.3 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 8.0.27 or later.
See remediation →
63/100
Remediation priority · Elevated

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 Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/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

Vulnerability in MySQL Cluster allows a high privileged attacker with physical access to the network segment to compromise the cluster. Successful exploitation requires human interaction from a person other than the attacker and can result in complete takeover of MySQL Cluster.

MitigationRestrict physical access to network segments hosting MySQL Cluster and limit high-privilege access. Upgrade to a patched version when available from Oracle.

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
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
Adjacent
Complexity
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:H/UI:R/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. Confirm MySQL Cluster is installed
    Check for MySQL Cluster processes or binaries on the system. Look for mysqld processes with cluster-related parameters, or check installed packages/components that include 'mysql-cluster' in the name.
    Affected if MySQL Cluster software is present on the system
  2. Identify the MySQL Cluster version
    Run 'mysql --version' from a MySQL client or check the mysqld binary version. In MySQL Cluster, you can also query 'SELECT VERSION()' or 'SHOW VARIABLES LIKE 'version';' from a cluster management or data node.
    Affected if The version returned is between 8.0.0 and 8.0.27 inclusive
  3. Verify if NetApp Oncommand Insight uses MySQL Cluster
    Check the NetApp Oncommand Insight installation for bundled MySQL Cluster components. Consult the product documentation or check installed components.
    Affected if Oncommand Insight is installed and uses MySQL Cluster as its database backend
  4. Verify if NetApp Oncommand Workflow Automation uses MySQL Cluster
    Check the NetApp Oncommand Workflow Automation installation for bundled MySQL Cluster components. Consult the product documentation or check installed components.
    Affected if Oncommand Workflow Automation is installed and uses MySQL Cluster as its database backend
  5. Verify if NetApp Snapcenter uses MySQL Cluster
    Check the Netapp Snapcenter installation for bundled MySQL Cluster components. Consult the product documentation or check installed components.
    Affected if Snapcenter is installed and uses MySQL Cluster as its database backend

You are affected if you run MySQL Cluster version 8.0.0 through 8.0.27, or if any of the NetApp products (Oncommand Insight, Oncommand Workflow Automation, Snapcenter) are installed with MySQL Cluster components, given that the attacker has physical network access and can perform social engineering to obtain human interaction.

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

Restrict physical access to network segments hosting MySQL Cluster and limit high-privilege access. Upgrade to a patched version when available from Oracle.

Recommended fix Moderate confidence

MySQL Cluster 8.0.28 or later; NetApp products should consult respective NetApp advisories

  1. 1. Back up all MySQL Cluster data and configurations before proceeding with any upgrade.
  2. 2. Schedule a maintenance window as upgrades require downtime.
  3. 3. For MySQL Cluster: Upgrade MySQL Server from 8.0.0-8.0.27 to version 8.0.28 or later.
  4. 4. For NetApp products (Oncommand Insight, Oncommand Workflow Automation, Snapcenter): Check NetApp security advisory NTAP-20220120 for product-specific patches or contact NetApp support for remediation options.
  5. 5. After upgrade, verify MySQL Cluster services are running correctly.
  6. 6. Test application connectivity and functionality to ensure the upgrade did not break existing operations.
Caveat MySQL upgrade may require configuration adjustments; review MySQL 8.0 release notes for breaking changes between your current version and 8.0.28

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