dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21318

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.6.20 and prior and 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where 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:L/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

Local privilege escalation vulnerability in MySQL Cluster's general component (versions 7.6.20 and prior, 8.0.27 and prior). A high-privileged attacker with local system access can potentially achieve complete cluster takeover, but exploitation is difficult and requires human interaction from a person other than the attacker.

MitigationApply vendor patches (MySQL Cluster 7.6.21+ or 8.0.28+) when available. Until then, strictly limit local access to trusted high-privileged accounts and minimize opportunities for social engineering interactions with cluster administrators.

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.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
Local
Complexity
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Check if MySQL Cluster is installed
    Look for MySQL Cluster processes or binaries: run `ps aux | grep -i mysql` or check for ndb-related processes (ndb_mgmd, ndbd, ndbmtd). Also check common installation paths like /usr/local/mysql-cluster/, /opt/mysql/, or /var/lib/mysql/.
    Affected if MySQL Cluster processes or binaries are found on the system
  2. Determine installed MySQL Cluster version
    Run `mysql --version` or for cluster-specific binaries: `ndb_mgmd --version` or `ndb_mgm --version`. If MySQL client is available, connect and run `SELECT VERSION();` to get the exact version string.
    Affected if The version returned is 7.6.0 through 7.6.20, or 8.0.0 through 8.0.27
  3. Check for NetApp Oncommand Insight
    Search for Oncommand Insight installation: look for processes named 'oci' or check common installation directories like /opt/NetApp/ or /opt/oci/. Check running services with `systemctl list-units --type=service | grep -i oncommand` or `ls -la /opt/` for NetApp directories.
    Affected if Oncommand Insight software is installed (all versions are affected)
  4. Check for NetApp Oncommand Workflow Automation
    Search for Oncommand Workflow Automation: look for processes or services containing 'oncwf' or 'workflow-automation'. Check installation directories similar to Oncommand Insight.
    Affected if Oncommand Workflow Automation software is installed (all versions are affected)

The environment is affected if MySQL Cluster versions 7.6.0-7.6.20 or 8.0.0-8.0.28 are installed, or if NetApp Oncommand Insight or Oncommand Workflow Automation are present (any 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

Apply vendor patches (MySQL Cluster 7.6.21+ or 8.0.28+) when available. Until then, strictly limit local access to trusted high-privileged accounts and minimize opportunities for social engineering interactions with cluster administrators.

Recommended fix Moderate confidence

MySQL Cluster 7.6.21+ or 8.0.28+ (or latest 8.0.x/8.1.x); NetApp - refer to NetApp advisory for fixed releases

  1. For MySQL Cluster: Upgrade MySQL Cluster from version 7.6.0-7.6.20 to version 7.6.21 or later, or upgrade from version 8.0.0-8.0.28 or later
  2. For NetApp Oncommand Insight: Apply the appropriate NetApp patch or upgrade to a fixed release as specified in NetApp's security advisory on security.netapp.com
  3. For NetApp Oncommand Workflow Automation: Apply the appropriate NetApp patch or upgrade to a fixed release as specified in NetApp's security advisory on security.netapp.com
  4. After upgrading, verify the MySQL Cluster version using: SELECT VERSION();
  5. Confirm the vulnerability is resolved by reviewing the change log for the new MySQL Cluster version
Caveat Standard MySQL upgrade precautions apply - review upgrade guide, test in staging environment before production deployment, ensure backups are in place

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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