dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21280

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
High EPSS

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

This is a vulnerability in the MySQL Cluster product's Cluster:General component affecting versions 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior, and 8.0.27 and prior. The flaw allows a high-privileged attacker with physical access to the communication segment attached to the hardware where MySQL Cluster executes to compromise the cluster, potentially achieving full takeover. Exploitation is difficult, requiring both physical proximity access and human interaction from a non-attacker person.

MitigationUpgrade MySQL Cluster to version 8.0.28 or later (and corresponding patched versions for 7.4.x, 7.5.x, 7.6.x branches). Additionally, enforce strict physical security controls on network segments and hardware hosting the cluster to reduce attack surface.

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 is installed
    Check for ndbd or ndbmtd processes running, or look for MySQL Cluster binaries in common installation paths like /usr/sbin/ndbd, /usr/bin/mysql, or check for ndbcluster in my.cnf configuration files.
    Affected if MySQL Cluster binaries or ndbcluster configuration is found on the system.
  2. Determine the installed MySQL Cluster version
    Run 'mysql --version' or check the ndbd --version output if available, or inspect the installed RPM/deb package version using package manager commands like 'rpm -qa | grep mysql-cluster' or 'dpkg -l | grep mysql-cluster'.
    Affected if The version number returned is 7.4.x at 34 or lower, 7.5.x at 24 or lower, 7.6.x at 20 or lower, or 8.0.x at 27 or lower.
  3. Verify the Cluster:General component is in use
    Check the my.cnf configuration file for the ndbcluster storage engine being enabled (look for 'ndbcluster' under [mysqld] section) and check for ndb-connectstring parameters pointing to management nodes.
    Affected if The ndbcluster storage engine is enabled in the MySQL configuration.
  4. Check physical access exposure
    Review network documentation and physical security controls to determine if the network segment connected to the MySQL Cluster hardware is accessible to unauthorized high-privileged users.
    Affected if The hardware hosting MySQL Cluster or its communication network segment lacks physical security controls or is accessible to non-authorized personnel.

You are affected if MySQL Cluster with ndbcluster enabled is running a version within 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, and the hardware or its network segment has insufficient physical access controls.

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 version 8.0.28 or later (and corresponding patched versions for 7.4.x, 7.5.x, 7.6.x branches). Additionally, enforce strict physical security controls on network segments and hardware hosting the cluster to reduce attack surface.

Recommended fix Moderate confidence

MySQL Cluster 7.4.35+/7.5.25+/7.6.21+/8.0.28+ (first version beyond each affected branch)

  1. 1. Identify the currently running MySQL Cluster version using 'mysql --version' or checking the ndb_mgmd process
  2. 2. Plan maintenance window as this upgrade requires cluster downtime
  3. 3. Backup all MySQL Cluster data using mysqldump orndb_desc backup
  4. 4. For MySQL Cluster 7.4.x: Upgrade to version 7.4.35 or later
  5. 5. For MySQL Cluster 7.5.x: Upgrade to version 7.5.25 or later
  6. 6. For MySQL Cluster 7.6.x: Upgrade to version 7.6.21 or later
  7. 7. For MySQL Cluster 8.0.x: Upgrade to version 8.0.28 or later
  8. 8. Download MySQL Cluster from official Oracle MySQL downloads page
Caveat Minor version upgrades typically maintain compatibility but test in staging first; OnCommand products may require vendor-supplied patches from NetApp

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
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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