dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21284

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's general component allows a high-privileged attacker with physical access to the network segment attached to the hardware where MySQL Cluster runs to compromise the cluster. Successful exploitation requires human interaction from a person other than the attacker and can result in complete takeover (full confidentiality, integrity, and availability compromise). The attack is characterized as difficult to exploit due to high attack complexity (AC:H), required user interaction (UI:R), and adjacent attack vector (AV:A).

MitigationApply Oracle's patched versions: upgrade to MySQL Cluster 7.4.35 or later, 7.5.25 or later, 7.6.21 or later, or 8.0.28 or later. Additionally, enforce strict physical security of the data center and network segmentation to limit access to the communication segment.

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` from the MySQL server host, or connect to MySQL and run `SELECT VERSION();` to retrieve the exact version string.
    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 product is MySQL Cluster
    Check if the MySQL installation is the Cluster variant by querying `SHOW VARIABLES LIKE 'have_clustering';` or checking the product edition in the version string.
    Affected if The product is MySQL Cluster and the version is in the affected ranges.
  3. Check for NetApp Oncommand Insight
    Locate installed software on systems running Oncommand Insight. On Windows, check Programs and Features; on Linux, run `rpm -qa | grep -i oncommand` or `dpkg -l | grep -i oncommand`.
    Affected if Oncommand Insight is installed, regardless of version (all versions affected).
  4. Check for NetApp Oncommand Workflow Automation
    Locate installed software on systems running Oncommand Workflow Automation. On Windows, check Programs and Features; on Linux, run `rpm -qa | grep -i oncommand` or `dpkg -l | grep -i oncommand`.
    Affected if Oncommand Workflow Automation is installed, regardless of version (all versions affected).
  5. Assess network attack surface
    Review network segmentation and physical access controls. Verify whether the MySQL Cluster communication ports (typically 1186 for cluster management, 3306 for MySQL, and data node ports) are accessible from adjacent network segments beyond the trusted data center network.
    Affected if The cluster is reachable from an adjacent network segment without proper isolation, and the product version is in the affected range.

The environment is affected if running MySQL Cluster versions 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, OR if NetApp Oncommand Insight or Oncommand Workflow Automation is installed at any version, AND the network segment is accessible to adjacent attackers.

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 Oracle's patched versions: upgrade to MySQL Cluster 7.4.35 or later, 7.5.25 or later, 7.6.21 or later, or 8.0.28 or later. Additionally, enforce strict physical security of the data center and network segmentation to limit access to the communication segment.

Recommended fix High confidence

MySQL Cluster 7.4.35+, 7.5.25+, 7.6.21+, or 8.0.28+ (depending on your current branch)

  1. Upgrade MySQL Cluster 7.4.x to version 7.4.35 or later
  2. Upgrade MySQL Cluster 7.5.x to version 7.5.25 or later
  3. Upgrade MySQL Cluster 7.6.x to version 7.6.21 or later
  4. Upgrade MySQL Cluster 8.0.x to version 8.0.28 or later
  5. For NetApp Oncommand Insight and Oncommand Workflow Automation, consult NetApp's security advisories at security.netapp.com for specific patch availability and upgrade paths
Caveat Review Oracle MySQL Cluster upgrade documentation for compatibility considerations between major versions; test upgrade in non-production environment first

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

Fix this in MySQL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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