MySQLDatabase / datastore · Oracle
CVE-2022-21290
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 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 · moderate confidenceCVE-2022-21290 is a vulnerability in MySQL Cluster (component: Cluster: General) affecting versions 8.0.27 and prior. It allows a high-privileged attacker with physical access to the network segment attached to the hardware where MySQL Cluster runs to achieve complete takeover of the cluster, but requires human interaction from a person other than the attacker.
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
>= 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.
-
Confirm MySQL Cluster is deployedCheck if the MySQL installation is using Cluster or NDB (Network Database) engine. Run: SHOW ENGINES; and look for 'ndbcluster' in the Support column. Also check for ndb_mgmd or ndbd processes running on the system.Affected if ndbcluster engine is present and the MySQL Cluster service is running
-
Check MySQL Cluster versionExecute: SELECT @@version; or mysqld --version on the management node. For MySQL Cluster, the version typically shows as '8.0.x' with 'Cluster' suffix.Affected if The version is 8.0.27 or earlier (8.0.0 through 8.0.27 inclusive)
-
Verify NetApp Oncommand Insight is in useCheck installed software on systems running NetApp Oncommand Insight. Look for the OCI application directory or service process.Affected if NetApp Oncommand Insight is installed (all versions are affected)
-
Verify NetApp Oncommand Workflow Automation is in useCheck installed software on systems running NetApp Oncommand Workflow Automation. Look for the WFA application directory or service process.Affected if NetApp Oncommand Workflow Automation is installed (all versions are affected)
-
Assess network exposureReview network segmentation and physical access controls. Check if the network segment hosting the MySQL Cluster management/data nodes is accessible to untrusted personnel. Examine firewall rules and port exposures (ports 1186, 2200-2207 for Cluster communications).Affected if The cluster network segment is reachable by untrusted users or lacks physical access controls
You are affected if you run MySQL Cluster version 8.0.0-8.0.27, or any version of NetApp Oncommand Insight or Workflow Automation, and the cluster network has insufficient physical/access controls.
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 access to network infrastructure, implement strict network segmentation, apply least-privilege principles to user accounts, and upgrade MySQL Cluster to a patched version when available.
MySQL 8.0.28 or later (for MySQL Cluster); Contact NetApp for Oncommand product patches
- For MySQL Cluster: Upgrade MySQL to version 8.0.28 or later to resolve the vulnerability
- For Oncommand Insight and Oncommand Workflow Automation: Contact NetApp support for specific patch availability as no fixed version details were provided in the reference material
- After upgrading, verify the MySQL Cluster version using: SELECT VERSION();
- Test the upgrade in a staging environment before applying to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MySQL
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21290 — 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-21290 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