dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21329

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'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. Allows a high-privileged attacker with physical access to the network segment attached to the hardware where MySQL Cluster runs to compromise the cluster, potentially achieving full takeover. Exploitation is difficult, requiring human interaction from a person other than the attacker.

MitigationApply the Oracle Critical Patch Update addressing CVE-2022-21329, or upgrade MySQL Cluster to version 8.0.28 or later (or equivalent patched versions in 7.4/7.5/7.6 branches). Restrict physical access to the cluster's network segment as an additional compensating control.

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 MySQL Cluster installation and version
    Run 'mysql --version' or check the MySQL server version. For MySQL Cluster, check the ndb_mgm client version (ndb_mgm -e 'SHOW'). Alternatively, query SELECT VERSION() from a MySQL client connected to the cluster.
    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.
  2. Confirm Cluster: General component is in use
    Verify that the MySQL Cluster (NDB) storage engine is active. Query 'SHOW ENGINES' and check for NDB or NDBCLUSTER engine with 'Support' set to 'YES' or 'DEFAULT'.
    Affected if The NDB Cluster storage engine is enabled and actively used in the database.
  3. Check NetApp Oncommand Insight installation
    On the system running Oncommand Insight, check for the installation directory (commonly /opt/oci or C:\Program Files\OnCommand Insight) and the installed software via system inventory or package manager.
    Affected if Oncommand Insight is installed on any version.
  4. Check NetApp Oncommand Workflow Automation installation
    On the system running Oncommand Workflow Automation, check for the installation directory and verify the software presence via system inventory or package manager.
    Affected if Oncommand Workflow Automation is installed on any version.
  5. Assess network segment exposure
    Review network configuration and access controls. Check if the cluster's network segment (management, data, or API network) is accessible to unauthorized high-privileged attackers on the same physical network segment.
    Affected if The MySQL Cluster network segment is accessible to untrusted high-privileged users or systems outside the trusted administrative zone.

You are affected if you run MySQL Cluster versions 7.4.34 and prior, 7.5.24 and prior, 7.6.20 and prior, or 8.0.27 and prior with the NDB Cluster engine enabled, or if you have NetApp Oncommand Insight or Oncommand Workflow Automation installed, and the cluster network segment can be accessed by untrusted high-privileged attackers.

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 Oracle Critical Patch Update addressing CVE-2022-21329, or upgrade MySQL Cluster to version 8.0.28 or later (or equivalent patched versions in 7.4/7.5/7.6 branches). Restrict physical access to the cluster's network segment as an additional compensating control.

Recommended fix High confidence

MySQL Cluster 7.4.35+, 7.5.25+, 7.6.21+, or 8.0.28+ (8.0.29 recommended)

  1. 1. Identify the exact MySQL Cluster version currently installed by running 'mysql --version' or checking the MySQL service
  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 (8.0.29 recommended)
  6. 6. For NetApp Oncommand Insight and Oncommand Workflow Automation: Contact NetApp support for specific patch availability as these products bundle MySQL Cluster
Caveat Review MySQL Cluster upgrade documentation for potential compatibility considerations; test upgrades in non-production environment first

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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