dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21285

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 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 where MySQL Cluster operates to compromise the cluster, requiring human interaction from another person for successful exploitation.

MitigationRestrict physical access to network infrastructure and ensure proper network segmentation; upgrade to patched MySQL Cluster versions beyond 8.0.27 or the respective fixed versions for 7.4/7.5/7.6 branches.

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
    Run 'mysql --version' or check for ndb* processes (ndbd, ndb_mgmd) or look for MySQL Cluster directories in /var/lib/mysql or Program Files/MySQL. On NetApp systems, check for Oncommand Insight or Oncommand Workflow Automation installations.
    Affected if MySQL Cluster or NetApp Oncommand products are installed
  2. Determine MySQL Cluster version
    Run 'mysql -u root -p -e "SELECT @@version;"' to get the MySQL version. For ndbd processes, check 'ndb_mgmd --version' or use ndb_mgm -e 'SHOW'. Compare output to affected version ranges: 7.4.x <= 7.4.34, 7.5.x <= 7.5.24, 7.6.x <= 7.6.20, 8.0.x <= 8.0.27.
    Affected if Version falls within any of the affected ranges listed
  3. Confirm cluster configuration
    Check if ndbcluster storage engine is enabled: run 'mysql -u root -p -e "SHOW ENGINES;"' and look for ndbcluster in the Support column. Also verify ndbd/ndb_mgmd processes are running.
    Affected if ndbcluster engine is present and cluster processes are active
  4. For NetApp products specifically
    On NetApp systems, verify if Oncommand Insight or Oncommand Workflow Automation is installed. Check installed packages or program directories for these products. NetApp lists all versions as affected.
    Affected if Either Oncommand Insight or Oncommand Workflow Automation is installed (any version)

You are affected if MySQL Cluster version is 7.4.34 or lower, 7.5.24 or lower, 7.6.20 or lower, or 8.0.27 or lower, or if NetApp Oncommand Insight/Workflow Automation is installed regardless of 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 network infrastructure and ensure proper network segmentation; upgrade to patched MySQL Cluster versions beyond 8.0.27 or the respective fixed versions for 7.4/7.5/7.6 branches.

Recommended fix High confidence

MySQL Cluster 8.0.28+ (or 7.4.35+/7.5.25+/7.6.21+ depending on branch); NetApp products contact vendor for patch

  1. 1. Identify the specific MySQL Cluster version in use by running: `SELECT VERSION();` or checking the ndbinfo database
  2. 2. For MySQL Cluster 8.0.x: Upgrade to MySQL Cluster 8.0.28 or later from https://dev.mysql.com/downloads/cluster/
  3. 3. For MySQL Cluster 7.4.x: Upgrade to version 7.4.35 or later
  4. 4. For MySQL Cluster 7.5.x: Upgrade to version 7.5.25 or later
  5. 5. For MySQL Cluster 7.6.x: Upgrade to version 7.6.21 or later
  6. 6. For NetApp Oncommand Insight: Apply the relevant NetApp patch from security.netapp.com (this product is End-of-Life - consider migration)
  7. 7. For NetApp Oncommand Workflow Automation: Apply the relevant NetApp patch from security.netapp.com (this product is End-of-Life - consider migration)
  8. 8. After upgrade, verify the version and test cluster functionality
Caveat Minor - this is a patch升级; review Oracle MySQL Cluster 8.0.28 release notes for any replication or configuration changes; NetApp Oncommand products are End-of-Life with limited support options

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

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 locally
dbcve dependency scanner

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