dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21326

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 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior and 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

A vulnerability in MySQL Cluster's Cluster: General component allows a high-privileged attacker with physical access to the network segment to compromise the cluster, potentially resulting in complete takeover. Exploitation is difficult, requiring human interaction and adjacency to the hardware.

MitigationUpgrade MySQL Cluster to a version beyond 8.0.27 (or the equivalent patched version for 7.4/7.5/7.6 branches). Restrict physical and network access to the cluster communication segments.

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:>= 7.4.0, <= 7.4.34>= 7.5.0, <= 7.5.24>= 7.6.0, <= 7.6.20>= 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
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. Identify if MySQL Cluster (NDB) is installed
    Check for ndbd, ndb_mgmd, or ndbapi processes running on the system, or look for MySQL Cluster directories in /usr/local/mysql-cluster or /opt/mysql/
    Affected if MySQL Cluster processes are running and the Cluster: General component is present
  2. Determine the MySQL Cluster version
    Run 'mysql --version' from the MySQL client, or connect and execute 'SELECT VERSION();' or 'SELECT @@version;'. For NDB-specific version, run 'SELECT * FROM ndbinfo.info;'
    Affected if The version falls within 7.4.0-7.4.34, 7.5.0-7.5.24, 7.6.0-7.6.20, or 8.0.0-8.0.27
  3. Check if NetApp Oncommand Insight is installed
    Look for Oncommand Insight installation directories, check for Java processes related to OCI, or examine installed software listings
    Affected if NetApp Oncommand Insight of any version is installed and running
  4. Check if NetApp Oncommand Workflow Automation is installed
    Look for Oncommand Workflow Automation installation directories, check for associated services or Java processes
    Affected if NetApp Oncommand Workflow Automation of any version is installed and running
  5. Verify cluster communication exposure
    Review network configuration to determine if cluster communication ports (1186 for ndbd, 2200+ range for mgmd) are accessible beyond trusted segments
    Affected if Cluster inter-node communication is accessible from network segments accessible to unauthorized high-privileged attackers

You are affected if MySQL Cluster 7.4.x up to 7.4.34, 7.5.x up to 7.5.24, 7.6.x up to 7.6.20, or 8.0.x up to 8.0.27 is running, or if NetApp Oncommand Insight or Oncommand Workflow Automation of any version is installed, and the cluster network segment is reachable by a high-privileged attacker with physical access.

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 Cluster to a version beyond 8.0.27 (or the equivalent patched version for 7.4/7.5/7.6 branches). Restrict physical and network access to the cluster communication segments.

Recommended fix Moderate confidence

MySQL Cluster 8.0.28 (or 7.4.35+/7.5.25+/7.6.21+ for respective branches)

  1. Identify the current MySQL Cluster version in use using 'SELECT VERSION();' or ndb_desc utility
  2. For MySQL Cluster 7.4.x: Upgrade to MySQL Cluster 7.4.35 or later
  3. For MySQL Cluster 7.5.x: Upgrade to MySQL Cluster 7.5.25 or later
  4. For MySQL Cluster 7.6.x: Upgrade to MySQL Cluster 7.6.21 or later
  5. For MySQL Cluster 8.0.x: Upgrade to MySQL Cluster 8.0.28 or later
  6. For NetApp Oncommand Insight and Oncommand Workflow Automation: Consult NetApp security advisory for product-specific patches
  7. After upgrade, verify the new version is running and test application functionality
Caveat MySQL Cluster upgrades may require cluster restart and can have compatibility implications; review Oracle MySQL Cluster release notes before upgrading

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

Fix this in MySQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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