MySQLDatabase / datastore · Oracle

CVE-2022-21320

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

NVD · unedited

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 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

dbcve analysis · high confidence

This is a vulnerability in MySQL Cluster (component: Cluster: General) affecting versions 8.0.27 and prior. It allows a high-privileged attacker with physical access to the network segment attached to the MySQL Cluster hardware to potentially takeover the cluster. Exploitation is difficult and requires human interaction from a person other than the attacker.

MitigationUpgrade MySQL Cluster to a patched version (8.0.28 or later). In the meantime, ensure strong physical security of the data center and network segmentation to limit access to the physical communication segment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

MySQLDatabase / datastore

Affected:>= 8.0.0, <= 8.0.27

Oncommand InsightApplication

Affected:all versions

Oncommand Workflow AutomationApplication

Affected:all versions

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check installed MySQL Server version

Run `mysql --version` or connect to MySQL and execute `SELECT VERSION();` to retrieve the exact version number

Affected if Version is 8.0.27 or earlier (8.0.0 through 8.0.27 inclusive)
Verify MySQL Cluster component is in use

Check if the NDB cluster engine is enabled: run `SHOW ENGINES;` and look for 'ndbcluster' with 'YES' status, or check for ndbd/ndbmtd processes with `ps aux | grep ndb`

Affected if NDB cluster engine (ndbcluster) is installed and active, indicating MySQL Cluster is configured
Confirm MySQL Cluster specific version

If Cluster is in use, query `SELECT @@ndb_version_string;` or `SELECT @@version_comment;` to confirm the NDB cluster version component

Affected if The NDB cluster version component matches the vulnerable 8.0.x range through 8.0.27
Check for NetApp Oncommand Insight installation

On the affected system, query installed packages or check for Oncommand Insight binaries (commonly in /opt/netapp or Program Files/NetApp)

Affected if Netapp Oncommand Insight is installed, regardless of version (all versions affected)
Check for NetApp Oncommand Workflow Automation installation

On the affected system, query installed packages or check for Oncommand Workflow Automation binaries

Affected if Netapp Oncommand Workflow Automation is installed, regardless of version (all versions affected)

You are affected if you run MySQL Cluster version 8.0.0 through 8.0.27, or if you have NetApp Oncommand Insight or NetApp Oncommand Workflow Automation installed, AND an attacker could gain physical access to the cluster's network segment.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 8.0.27

Interim mitigation

Upgrade MySQL Cluster to a patched version (8.0.28 or later). In the meantime, ensure strong physical security of the data center and network segmentation to limit access to the physical communication segment.

Recommended fix Moderate confidence

MySQL Cluster 8.0.28 or later (or latest 8.0.x stable release)

Identify the exact MySQL Cluster version currently installed using: SELECT VERSION();
Review the Oncommand Insight and Oncommand Workflow Automation documentation to confirm they embed MySQL and are therefore affected
For MySQL Cluster: Plan upgrade to MySQL Cluster 8.0.28 or later (the next release after 8.0.27 which contains the fix)
For NetApp products: Check security.netapp.com for specific patch advisories for Oncommand Insight and Oncommand Workflow Automation
Test the upgrade in a non-production environment before deploying to production
Schedule a maintenance window and perform the upgrade
After upgrade, verify the MySQL Cluster is operational and test application functionality

Caveat Standard MySQL upgrade precautions apply - review Oracle's upgrade documentation for backup and compatibility checks

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-21320 — 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

Primary sources

www.oracle.comVendor Advisory
security.netapp.comThird Party Advisory
www.zerodayinitiative.comThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21320 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-21320?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 8.0.27 or later

Severity 6.3 Medium

Exploit likelihood EPSS, next 30 days 2.7%

Affects: MySQL

Remediation

Need this fixed?

Fix this in MySQL 40 hrs · Moderate

Typical engagement from $7,000

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-21320 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References