dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21330

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.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 General component allowing a high-privileged attacker with physical access to the communication segment attached to the hardware to compromise the cluster. Difficult to exploit with human interaction required; successful exploitation results in complete takeover (full confidentiality, integrity, and availability impact).

MitigationRestrict physical access to the network segment where MySQL Cluster executes. Apply Oracle Critical Patch Update (CPU) patches for January 2022 or later, upgrading beyond affected versions (7.5.24, 7.6.20, 8.0.27). Implement network segmentation and physical security controls for the cluster infrastructure.

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.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
    Run command 'mysql --version' or check for 'ndb' processes (ndbd, ndb_mgmd) via 'ps aux | grep ndb' or check for MySQL Cluster service
    Affected if MySQL Cluster (ndb) processes or binaries are found on the system
  2. Check MySQL Cluster version
    Execute 'mysql -e "SELECT @@version_comment;"' or check MySQL Cluster manager (ndb_mgmd) version via 'ndb_mgmd --version'
    Affected if Version falls within 7.5.0-7.5.24, 7.6.0-7.6.20, or 8.0.0-8.0.27
  3. Verify affected General component is in use
    Confirm the MySQL Cluster General component (ndb_general) is active by checking cluster status via 'ndb_mgm -e "show"'
    Affected if MySQL Cluster is operational and the General component is loaded
  4. Check for NetApp Oncommand Insight installation
    Search for Oncommand Insight installation directories or check installed software inventory (e.g., 'ls /opt/NetApp/ocp' or similar paths, or check Windows Program files)
    Affected if Oncommand Insight software is installed (all versions affected)
  5. Check for NetApp Oncommand Workflow Automation installation
    Search for Oncommand Workflow Automation installation or check installed software inventory
    Affected if Oncommand Workflow Automation software is installed (all versions affected)

System is affected if running MySQL Cluster versions 7.5.0-7.5.24, 7.6.0-7.6.20, or 8.0.0-8.0.27, OR if NetApp Oncommand Insight or Oncommand Workflow Automation is installed at any version.

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 the network segment where MySQL Cluster executes. Apply Oracle Critical Patch Update (CPU) patches for January 2022 or later, upgrading beyond affected versions (7.5.24, 7.6.20, 8.0.27). Implement network segmentation and physical security controls for the cluster infrastructure.

Recommended fix High confidence

MySQL Cluster 7.5.25+, 7.6.21+, or 8.0.28+ (depending on your current branch)

  1. 1. Backup all MySQL Cluster data and configuration files before making any changes
  2. 2. Schedule a maintenance window as upgrade will require cluster downtime
  3. 3. For MySQL Cluster 7.5.x: Upgrade to MySQL Cluster 7.5.25 or later
  4. 4. For MySQL Cluster 7.6.x: Upgrade to MySQL Cluster 7.6.21 or later
  5. 5. For MySQL Cluster 8.0.x: Upgrade to MySQL Cluster 8.0.28 or later
  6. 6. After upgrade, verify cluster health status using ndb_mgm management tool
  7. 7. Test application connectivity and functionality
  8. 8. For NetApp Oncommand Insight and Oncommand Workflow Automation: These products are end-of-life with no patch available; consider migrating to supported alternatives
Caveat Review Oracle MySQL Cluster upgrade documentation for any configuration or compatibility changes between versions; test thoroughly in staging before production deployment

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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