dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21287

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 allows a high-privileged attacker with physical network access to the hardware where MySQL Cluster executes to compromise the cluster. Exploitation is difficult, requires human interaction, and successful attacks result in complete takeover with high impact to confidentiality, integrity, and availability.

MitigationApply Oracle's patches to upgrade MySQL Cluster beyond affected versions (8.0.27, 7.6.20, 7.5.24, 7.4.34). Restrict physical access to the network segments and limit high-privileged account access to reduce attack surface.

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 if MySQL Cluster is installed
    Run 'mysql --version' or check for MySQL Cluster service processes such as ndb_mgmd, ndbd, or ndbmtd. On Linux, also check /var/lib/mysql or /usr/local/mysql directories.
    Affected if MySQL Cluster binaries or services are found on the system
  2. Determine MySQL Cluster version
    Execute 'mysql --version' from the MySQL binary directory, or connect to the cluster management node (ndb_mgm) and run 'SHOW' to retrieve version information.
    Affected if The reported 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
  3. Check if MySQL Cluster General component is in use
    Query MySQL with 'SHOW ENGINE NDB STATUS' or check for NDB Cluster tables in the mysql schema. Verify the cluster is actively managing data via the NDB storage engine.
    Affected if NDB Cluster engine is active and the cluster is operational with the vulnerable versions listed above
  4. Identify NetApp Oncommand Insight installation
    Check for Oncommand Insight installation directories (commonly C:\Program Files\NetApp\Oncommand Insight or /opt/netapp/oci) and running services named 'OCI' or 'Oncommand Insight'.
    Affected if Oncommand Insight is installed (all versions are affected)
  5. Identify NetApp Oncommand Workflow Automation installation
    Check for Oncommand Workflow Automation directories and services, typically installed under C:\Program Files\NetApp\Oncommand Workflow Automation or /opt/netapp/owfa.
    Affected if Oncommand Workflow Automation is installed (all versions are affected)
  6. Verify physical network exposure
    Review network configuration to determine if the MySQL Cluster management and data nodes are accessible from untrusted physical network segments. Check firewall rules and network segregation controls.
    Affected if The cluster hardware is reachable from physical networks where untrusted users have access

The environment is affected if MySQL Cluster versions 7.4.x through 8.0.27, or any NetApp Oncommand Insight/Workflow Automation installation, are present AND the hardware is accessible to high-privileged attackers via physical network access.

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

Apply Oracle's patches to upgrade MySQL Cluster beyond affected versions (8.0.27, 7.6.20, 7.5.24, 7.4.34). Restrict physical access to the network segments and limit high-privileged account access to reduce attack surface.

Recommended fix Moderate confidence

MySQL Cluster 7.4.35 or later (7.4.x line), 7.5.25 or later (7.5.x line), 7.6.21 or later (7.6.x line), or 8.0.28 or later (8.0.x line)

  1. Identify the currently installed MySQL Cluster version using: SELECT VERSION();
  2. Based on the installed major version line, plan upgrade to the next available release: for 7.4.x upgrade to 7.4.35+, for 7.5.x upgrade to 7.5.25+, for 7.6.x upgrade to 7.6.21+, for 8.0.x upgrade to 8.0.28+
  3. For OnCommand Insight and OnCommand Workflow Automation, contact NetApp support for specific patch availability since all versions are affected
  4. Review MySQL Cluster upgrade documentation before performing upgrade
  5. Backup all data and configuration files before initiating upgrade
  6. Test upgrade in non-production environment first
  7. Execute upgrade following MySQL Cluster rolling upgrade procedures if zero-downtime is required
  8. Verify successful upgrade by checking: SELECT VERSION();
Caveat MySQL Cluster upgrades may require careful planning; review Oracle's upgrade guide for compatibility notes between minor versions

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

Fix this in MySQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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