CVE-2022-21490
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.35 and prior, 7.5.25 and prior, 7.6.21 and prior and 8.0.28 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 confidenceVulnerability in Oracle MySQL Cluster's general clustering component (Cluster: General). Allows a high-privileged attacker with physical access to the network segment where MySQL Cluster communicates to compromise the cluster. Exploitation is difficult, requires human interaction from a person other than the attacker, and can result in complete takeover of the MySQL Cluster.
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.00, <= 7.4.35>= 7.5.00, <= 7.5.25>= 7.6.00, <= 7.6.21>= 8.0.00, <= 8.0.28all versionsall 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 Oracle MySQL Cluster is installedRun 'mysql --version' or check for MySQL Cluster processes with 'ps aux | grep ndb' or look for ndbd/ndbmtd processesAffected if MySQL Cluster binaries or processes are found on the system
-
Determine the exact MySQL Cluster versionConnect to the cluster and run 'SELECT @@version;' or check the installed package version with 'rpm -qa | grep mysql-cluster' or 'dpkg -l | grep mysql-cluster'Affected if The version falls within 7.4.00-7.4.35, 7.5.00-7.5.25, 7.6.00-7.6.21, or 8.0.00-8.0.28
-
Identify NetApp products using MySQLCheck if NetApp Active Iq Unified Manager, Oncommand Insight, or Snapcenter are installed using 'rpm -qa' or 'dpkg -l' for respective package namesAffected if Any of these NetApp products are installed (all versions are affected)
-
Assess network exposure of cluster communicationReview firewall rules and network segmentation around port 1186 (MySQL Cluster management node) and data node ports. Check if the cluster interconnect network is accessible from untrusted segmentsAffected if The MySQL Cluster internal network is accessible from outside the trusted management and data node segments
You are affected if you run Oracle MySQL Cluster versions 7.4.00 through 7.4.35, 7.5.00 through 7.5.25, 7.6.00 through 7.6.21, or 8.0.00 through 8.0.28, or any version of NetApp Active Iq Unified Manager, Oncommand Insight, or Snapcenter, and the cluster communication network is reachable from your attacker.
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 · scopedRestrict physical and network access to the MySQL Cluster communication infrastructure, apply the latest Oracle Critical Patch Update to obtain a fixed version (beyond 8.0.28, 7.6.21, 7.5.25, or 7.4.35), and follow the principle of least privilege for database accounts.
MySQL Cluster 7.4.36, 7.5.26, 7.6.22, or 8.0.29 (depending on your current branch)
- Identify the current MySQL Cluster version by running: `SELECT VERSION();` or checking the ndbinfo or ndb_mgm output
- Determine which major version branch you are on (7.4.x, 7.5.x, 7.6.x, or 8.0.x)
- For MySQL Cluster 7.4.x (versions 7.4.00 through 7.4.35): Upgrade to version 7.4.36
- For MySQL Cluster 7.5.x (versions 7.5.00 through 7.5.25): Upgrade to version 7.5.26
- For MySQL Cluster 7.6.x (versions 7.6.00 through 7.6.21): Upgrade to version 7.6.22
- For MySQL Cluster 8.0.x (versions 8.0.00 through 8.0.28): Upgrade to version 8.0.29
- Download the appropriate MySQL Cluster installation package from MySQL Downloads (downloads.mysql.com)
- Follow standard MySQL Cluster upgrade procedures: stop the cluster, upgrade binaries, verify configuration compatibility, restart the cluster
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21490 — 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-21490 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