dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21489

MEDIUM · 6.3 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to after 8.0.28 or later.
See remediation →
63/100
Remediation priority · Elevated
High EPSS

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.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 · moderate confidence

Vulnerability in MySQL Cluster allows a high privileged attacker with physical access to the network segment where the cluster executes to compromise the cluster. Successful exploitation requires human interaction and results in complete takeover of MySQL Cluster, affecting confidentiality, integrity, and availability.

MitigationRestrict physical access to the network infrastructure and limit high-level privileges. Upgrade to a patched MySQL Cluster version beyond 7.4.35, 7.5.25, 7.6.21, or 8.0.28.

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.00, <= 7.4.35>= 7.5.00, <= 7.5.25>= 7.6.00, <= 7.6.21>= 8.0.00, <= 8.0.28
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions
SnapcenterApplication
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
    Check for MySQL Cluster-specific processes (ndbd, ndb_mgmd, ndbmtd) or check the MySQL version with 'mysqld --version' and confirm it is the Cluster distribution rather than standard MySQL Server
    Affected if MySQL Cluster 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
  2. Check NetApp Active IQ Unified Manager presence
    Check for installation or running processes related to Active IQ Unified Manager on the system
    Affected if Any version of NetApp Active IQ Unified Manager is installed (all versions affected)
  3. Check NetApp Oncommand Insight presence
    Check for installation or running processes related to Oncommand Insight on the system
    Affected if Any version of NetApp Oncommand Insight is installed (all versions affected)
  4. Check NetApp Snapcenter presence
    Check for installation or running processes related to Snapcenter on the system
    Affected if Any version of NetApp Snapcenter is installed (all versions affected)
  5. Verify physical access controls to cluster network
    Review network segmentation and physical access controls to the network segment where MySQL Cluster executes
    Affected if The network segment hosting the cluster is accessible to untrusted physical locations or attackers with physical access
  6. Identify high-privilege MySQL Cluster accounts
    Review MySQL Cluster user accounts with high-level privileges (such as root or DBA-level access)
    Affected if High-privilege accounts exist on the cluster and could be targeted by an attacker with physical network access

You are affected if MySQL Cluster with a version in the affected ranges is running, OR any version of NetApp Active IQ Unified Manager, Oncommand Insight, or Snapcenter is installed, AND an attacker could gain physical access to the network segment and compromise a high-privilege account.

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.28
Interim mitigation

Restrict physical access to the network infrastructure and limit high-level privileges. Upgrade to a patched MySQL Cluster version beyond 7.4.35, 7.5.25, 7.6.21, or 8.0.28.

Recommended fix High confidence

MySQL Cluster 7.4.36+, 7.5.26+, 7.6.22+, or 8.0.29+ depending on your current major version

  1. 1. Identify the exact MySQL Cluster version currently installed by running: SELECT VERSION(); or checking mysqld --version
  2. 2. For MySQL Cluster 7.4.x: Upgrade to MySQL Cluster 7.4.36 or later
  3. 3. For MySQL Cluster 7.5.x: Upgrade to MySQL Cluster 7.5.26 or later
  4. 4. For MySQL Cluster 7.6.x: Upgrade to MySQL Cluster 7.6.22 or later
  5. 5. For MySQL Cluster 8.0.x: Upgrade to MySQL Cluster 8.0.29 or later
  6. 6. Download the appropriate MySQL Cluster distribution from dev.mysql.com or Oracle MySQL Enterprise
  7. 7. Perform a full backup of the MySQL Cluster data before upgrading
  8. 8. Follow the MySQL Cluster upgrade documentation for your version to apply the upgrade
Caveat MySQL Cluster upgrades may require careful planning; review MySQL Cluster upgrade guide for compatibility notes and ensure proper backup before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MySQL Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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