dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21328

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

Vulnerability in MySQL Cluster allows a high-privileged attacker with physical access to the network segment where MySQL Cluster hardware operates to achieve complete takeover of the cluster. Exploitation is difficult, requires human interaction, and targets the Cluster:General component in versions 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior, and 8.0.27 and prior.

MitigationApply Oracle's security patches for this vulnerability and upgrade to a supported MySQL Cluster version beyond 8.0.27. Additionally, enforce strict physical security and network segmentation around cluster infrastructure to limit the adjacent attack vector.

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. Confirm MySQL Cluster is in use
    Run `ndb_mgm -e "SHOW"` or check for ndbd/ndbmtd/ndb_mgmd processes on cluster nodes. Alternatively, connect to any SQL node and run `SELECT VERSION();` - MySQL Cluster versions include 'MySQL Cluster' in the output.
    Affected if The system runs MySQL Cluster (ndb) rather than standard MySQL Server.
  2. Identify the MySQL Cluster version
    Run `ndb_mgm --version` on a management node, or query `SELECT VERSION();` from an SQL node. Compare the reported version against the affected ranges: 7.4.x through 7.4.34, 7.5.x through 7.5.24, 7.6.x through 7.6.20, or 8.0.x through 8.0.27.
    Affected if The installed 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 for NetApp Oncommand Insight installation
    On the affected system, look for Oncommand Insight installation directories (commonly under /opt/NetApp/ocict or similar paths) or check for oci* processes running on the host.
    Affected if Oncommand Insight is installed (all versions are affected).
  4. Check for NetApp Oncommand Workflow Automation installation
    On the affected system, look for Oncommand Workflow Automation installation directories or check for nwa* processes. Common paths include /opt/NetApp/nwa or /opt/netapp/wfa.
    Affected if Oncommand Workflow Automation is installed (all versions are affected).
  5. Assess network exposure of cluster infrastructure
    Review network configuration to determine whether the MySQL Cluster management and data nodes are accessible from network segments accessible to untrusted users. Check VLAN assignments, firewall rules, and physical network access controls around cluster hardware.
    Affected if The cluster network segment is accessible to attackers without physical security controls.

You are affected if MySQL Cluster version 7.4.x through 7.4.34, 7.5.x through 7.5.24, 7.6.x through 7.6.20, or 8.0.x through 8.0.27 is running, or if NetApp Oncommand Insight or Oncommand Workflow Automation is installed, and the cluster network lacks physical isolation.

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 Oracle's security patches for this vulnerability and upgrade to a supported MySQL Cluster version beyond 8.0.27. Additionally, enforce strict physical security and network segmentation around cluster infrastructure to limit the adjacent attack vector.

Recommended fix Moderate confidence

MySQL Cluster 8.0.28+ (or latest 8.0.x stable); for 7.4.x upgrade to 7.4.35+, 7.5.x to 7.5.25+, 7.6.x to 7.6.21+

  1. 1. Identify the exact MySQL Cluster version in use by running: `SELECT VERSION();` or checking the MySQL installation
  2. 2. For MySQL 7.4.x: upgrade to MySQL Cluster 7.4.35 or later
  3. 3. For MySQL 7.5.x: upgrade to MySQL Cluster 7.5.25 or later
  4. 4. For MySQL 7.6.x: upgrade to MySQL Cluster 7.6.21 or later
  5. 5. For MySQL 8.0.x: upgrade to MySQL Cluster 8.0.28 or later (preferably 8.0.x latest stable)
  6. 6. For NetApp Oncommand Insight: monitor NetApp security advisories for a patch; no direct fix available as of this CVE
  7. 7. For NetApp Oncommand Workflow Automation: monitor NetApp security advisories for a patch; no direct fix available as of this CVE
  8. 8. After upgrade, verify successful startup and cluster health using `ndb_mgm` management console
Caveat Upgrading MySQL Cluster can require cluster restart and may have compatibility considerations; review Oracle upgrade documentation before proceeding

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 / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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