dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21356

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 allows a high-privileged attacker with physical access to the network segment to compromise the cluster. Exploitation is difficult, requires human interaction from a person other than the attacker, and can result in complete takeover with high confidentiality, integrity, and availability impacts.

MitigationUpgrade MySQL Cluster to versions 7.4.35+, 7.5.25+, 7.6.21+, or 8.0.28+ and later. Restrict physical and network access to the cluster communication infrastructure.

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 version
    Run 'mysqld --version' or 'mysql --version' from the command line, or check the MySQL server package via system package manager (rpm -q mysql or dpkg -l mysql)
    Affected if The 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
  2. Confirm MySQL Cluster component is in use
    Check if the MySQL installation includes the Cluster or NDB storage engine by running 'SHOW ENGINES;' within the mysql client or checking for ndbd/ndbmtd processes
    Affected if The NDB Cluster engine is present and active
  3. Identify NetApp Oncommand Insight version
    Check installed software version via the Oncommand Insight web interface under Help > About, or query the installed packages on the host system
    Affected if Any version of Oncommand Insight is installed (all versions are affected)
  4. Identify NetApp Oncommand Workflow Automation version
    Check installed software version via the Oncommand Workflow Automation web interface under Help > About, or query the installed packages on the host system
    Affected if Any version of Oncommand Workflow Automation is installed (all versions are affected)
  5. Assess network exposure
    Review network configuration to determine if the MySQL Cluster management and data ports (default 1186 for management, 3306 for MySQL) are accessible from untrusted network segments
    Affected if Cluster communication ports are exposed to network segments where untrusted individuals have physical access

You are affected if any MySQL Cluster installation runs version 7.4.x through 8.0.27, or if any NetApp Oncommand Insight or Oncommand Workflow Automation instance is present, especially when cluster communications are accessible beyond trusted physical boundaries.

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

Upgrade MySQL Cluster to versions 7.4.35+, 7.5.25+, 7.6.21+, or 8.0.28+ and later. Restrict physical and network access to the cluster communication infrastructure.

Recommended fix High confidence

MySQL Cluster 7.4.35+, 7.5.25+, 7.6.21+, or 8.0.28+ (depending on your current branch); NetApp products require vendor guidance

  1. Identify the exact MySQL Cluster version currently installed using: mysql --version or mysqld --version
  2. For MySQL Cluster 7.4.x: Upgrade to version 7.4.35 or later
  3. For MySQL Cluster 7.5.x: Upgrade to version 7.5.25 or later
  4. For MySQL Cluster 7.6.x: Upgrade to version 7.6.21 or later
  5. For MySQL Cluster 8.0.x: Upgrade to version 8.0.28 or later
  6. For NetApp Oncommand Insight and Oncommand Workflow Automation: Contact NetApp support for vendor-specific patches; this vulnerability affects all versions and may require upgrading to a newer major release if patches are unavailable
  7. Test the upgrade in a non-production environment before deploying to production
  8. Backup all data and configurations before performing the upgrade
Caveat Standard MySQL upgrade precautions apply - test thoroughly in staging, review release notes for any behavioral changes, and ensure application compatibility

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

Fix this in MySQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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