dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21308

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 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 Oracle MySQL Cluster (versions 8.0.27 and prior) in the Cluster: General component. A high-privileged attacker with physical access to the network segment where MySQL Cluster operates can exploit this difficult-to-exploit flaw, which also requires human interaction from a person other than the attacker. Successful exploitation results in complete takeover of the MySQL Cluster with high impact to confidentiality, integrity, and availability.

MitigationApply the relevant Oracle Critical Patch Update or upgrade MySQL Cluster to a version beyond 8.0.27. Additionally, enforce strict physical security and network segmentation to limit access to the hardware and communication segments where MySQL Cluster executes.

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:>= 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 the installed MySQL server version
    Run 'mysql --version' or log into MySQL and execute 'SELECT VERSION();' to obtain the exact version string
    Affected if The version returned is between 8.0.0 and 8.0.27 inclusive
  2. Confirm MySQL Cluster is in use
    Check if the 'ndb' or 'ndbcluster' storage engine is available and in use. Run 'SHOW ENGINES;' or query 'SHOW VARIABLES LIKE 'have_ndbcluster';' in MySQL
    Affected if The ndbcluster engine is present and active, indicating MySQL Cluster is deployed
  3. Check for Netapp Oncommand Insight installation
    Inspect system for Netapp Oncommand Insight software components, typically installed on Windows or Linux servers. Look for installation directories or use system inventory tools
    Affected if Netapp Oncommand Insight is installed on the system
  4. Check for Netapp Oncommand Workflow Automation installation
    Inspect system for Netapp Oncommand Workflow Automation software components. Look for installation directories or use system inventory tools
    Affected if Netapp Oncommand Workflow Automation is installed on the system

A user is affected if they run Oracle MySQL Cluster version 8.0.0 through 8.0.27, or have Netapp Oncommand Insight or Netapp Workflow Automation installed, with the additional requirement that the attacker has physical access to the network segment and can leverage human interaction

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 the relevant Oracle Critical Patch Update or upgrade MySQL Cluster to a version beyond 8.0.27. Additionally, enforce strict physical security and network segmentation to limit access to the hardware and communication segments where MySQL Cluster executes.

Recommended fix Moderate confidence

MySQL 8.0.28 or later for the Cluster component

  1. 1. For MySQL Cluster: Upgrade MySQL Server from 8.0.27 or earlier to version 8.0.28 or later, as this version addresses the vulnerability in the Cluster component.
  2. 2. For NetApp Oncommand Insight and Oncommand Workflow Automation: These products are listed as affected with 'all versions'. Consult NetApp's security advisory (security.netapp.com) for specific remediation guidance, as these products may require alternative mitigation or may be end-of-life with no patch available.
  3. 3. If upgrading is not immediately feasible, implement network segmentation to restrict physical access to the communication segment where MySQL Cluster operates, as the CVSS vector indicates the attacker requires Adjacent (AV:A) network access.
Caveat MySQL 8.0.x upgrades typically have minimal breaking changes for most applications, but review Oracle's MySQL 8.0 release notes for any compatibility notes between 8.0.27 and the target upgrade version.

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