MySQLDatabase / datastore · Oracle

CVE-2022-21316

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

dbcve analysis · high confidence

Vulnerability in MySQL Cluster's Cluster:General component allows a high-privileged attacker with local infrastructure access to compromise the cluster through difficult-to-exploit means requiring human interaction. Successful exploitation grants complete takeover affecting confidentiality, integrity, and availability.

MitigationApply Oracle's patched MySQL Cluster version (8.0.28+, 7.6.21+, 7.5.25+, 7.4.35+) following Oracle's documented cluster upgrade procedures, ensuring compatibility testing in non-production first.

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:>= 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

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?

dbcve checks

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

Confirm MySQL Cluster is in use

Check if the MySQL Cluster service (mysqld with ndbcluster) or ndb_mgmd management daemon is running. Look for ndbd processes or check cluster status via 'ndb_mgm -e show' if available.

Affected if MySQL Cluster components are actively running on the system
Identify installed MySQL Cluster version

Run 'mysql --version' or 'mysqld --version' on the cluster node. For RPM packages, use 'rpm -qa | grep mysql'. For Debian packages, use 'dpkg -l | grep mysql'. Check the full version string including the cluster component version.

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
Check NetApp Oncommand Insight installation

On the host running Oncommand Insight, check for installed software version or running service. Look for installation directories or check installed packages via system package manager.

Affected if Oncommand Insight is installed and running (all versions are affected)
Check NetApp Oncommand Workflow Automation installation

On the host running Oncommand Workflow Automation, check for installed software version or running service. Look for installation directories or check installed packages via system package manager.

Affected if Oncommand Workflow Automation is installed and running (all versions are affected)

A system is affected if MySQL Cluster version is 7.4.x <= 34, 7.5.x <= 24, 7.6.x <= 20, or 8.0.x <= 27, OR if NetApp Oncommand Insight or Oncommand Workflow Automation is installed regardless of version.

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

Apply Oracle's patched MySQL Cluster version (8.0.28+, 7.6.21+, 7.5.25+, 7.4.35+) following Oracle's documented cluster upgrade procedures, ensuring compatibility testing in non-production first.

Recommended fix High confidence

MySQL Cluster 8.0.28 or later (or latest stable 8.0.x/7.6.x/7.5.x/7.4.x release beyond the affected versions)

1. Identify the exact MySQL Cluster version currently installed using: `mysql --version` or checking the MySQL service
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 (or latest 8.0.x stable release)
6. For Oncommand Insight and Oncommand Workflow Automation: Contact NetApp support for specific patch availability, as no fixed version is documented in the advisory
7. After upgrade, verify the new version is running: `mysql --version` and `SELECT VERSION();`
8. Test application functionality to ensure compatibility with the new MySQL Cluster version

Caveat Minor version upgrades within the same major branch typically have low risk, but test in staging first as some functionality changes may occur between major 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
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-21316 — 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-21316 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-21316?

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 1.1%

Affects: MySQL

Remediation

Need this fixed?

Fix this in MySQL 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-21316 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