CVE-2022-21380
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 · uneditedVulnerability 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 confidenceThis is a vulnerability in MySQL Cluster that allows a high-privileged attacker with physical access to the network segment to potentially take over the MySQL Cluster. The attack requires human interaction from a person other than the attacker and is described as difficult to exploit. Successful exploitation results in complete compromise of confidentiality, integrity, and availability.
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>= 7.4.0, <= 7.4.34>= 7.5.0, <= 7.5.24>= 7.6.0, <= 7.6.20>= 8.0.0, <= 8.0.27all versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if MySQL Cluster is installedCheck if the ndb (NDB Cluster) storage engine is available by running `SHOW ENGINES;` or checking for ndb processes with `ps aux | grep ndb`Affected if NDB Cluster engine is present and listed as available
-
Check MySQL Cluster versionRun `SELECT VERSION();` or check the mysqld binary version with `mysqld --version` to obtain the exact version numberAffected if 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
-
Confirm MySQL Cluster component is in useRun `SHOW STATUS LIKE 'Ndb_cluster_node_id';` to verify the NDB Cluster component is actively connected and in useAffected if The query returns a valid node ID, confirming active Cluster usage
-
Check for NetApp Oncommand Insight installationInspect installed software or running services for Oncommand Insight on the systemAffected if Oncommand Insight is installed (any version)
-
Check for NetApp Oncommand Workflow Automation installationInspect installed software or running services for Oncommand Workflow Automation on the systemAffected if Oncommand Workflow Automation is installed (any version)
Environment is affected if MySQL Cluster with NDB engine is running and its version is 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, or if either NetApp Oncommand Insight or Oncommand Workflow Automation is present at any version.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade MySQL Cluster to a patched version (8.0.28 or higher for the 8.0 branch). Additionally, restrict physical access to the network infrastructure and implement network segmentation to limit exposure to adjacent network attacks.
MySQL Cluster 7.4.35 or later, 7.5.25 or later, 7.6.21 or later, 8.0.28 or later (depending on your current major version)
- 1. Identify the currently installed MySQL Cluster version using: `SELECT VERSION();` or checking the MySQL installation
- 2. Determine the appropriate upgrade path based on your current major version (7.4.x → 7.4.35+, 7.5.x → 7.5.25+, 7.6.x → 7.6.21+, 8.0.x → 8.0.28+)
- 3. Before upgrading, backup all MySQL Cluster data using appropriate tools such as mysqldump or MySQL Enterprise Backup
- 4. Review Oracle's MySQL Cluster upgrade documentation for your specific version path
- 5. Download and install the fixed MySQL Cluster version from Oracle's official downloads (https://www.oracle.com/downloads/) or your organization's package manager
- 6. After installation, verify the upgrade was successful by running `SELECT VERSION();`
- 7. For NetApp OnCommand Insight and OnCommand Workflow Automation, apply vendor-supplied patches when available from NetApp support
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21380 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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