dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2022-21482

MEDIUM · 6.3 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to after 8.0.28 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.28 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

A vulnerability in MySQL Cluster (versions 8.0.28 and prior) allows a high-privileged attacker with physical access to the network segment where the cluster operates to compromise the cluster through difficult-to-exploit attacks requiring human interaction from a third party. The attack results in complete takeover of MySQL Cluster with high impact to confidentiality, integrity, and availability.

MitigationUpgrade MySQL Cluster to a patched version (8.0.29 or later) and ensure physical security of the network infrastructure hosting the cluster. Restrict physical access to the communication segments and limit high-privilege access.

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.28
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions
SnapcenterApplication
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 if MySQL Cluster is installed
    Check for the presence of MySQL Cluster components on the system. On Linux, you can use 'rpm -qa | grep mysql' or 'dpkg -l | grep mysql' to list installed MySQL packages. Look for packages containing 'cluster' in the name.
    Affected if MySQL Cluster packages are found on the system
  2. Determine the installed MySQL Cluster version
    Run the command 'mysql --version' or access MySQL and execute 'SELECT VERSION();' to retrieve the exact version number. Alternatively, check the RPM/Debian package version with 'rpm -q mysql-cluster' or the equivalent package manager command.
    Affected if The version returned is between 8.0.0 and 8.0.28 inclusive
  3. Check for NetApp Active Iq Unified Manager
    Verify if NetApp Active Iq Unified Manager is installed on the system. Check for the service process or installation directory. On Windows, look in Program Files; on Linux, check common installation paths like /opt/netapp or /usr/local/netapp.
    Affected if NetApp Active Iq Unified Manager is present on the system (all versions are affected)
  4. Check for NetApp Oncommand Insight
    Verify if NetApp Oncommand Insight is installed. Look for the service executable or installation directory. Check running processes for 'oncommand' or 'oci' related entries.
    Affected if NetApp Oncommand Insight is present on the system (all versions are affected)
  5. Check for NetApp Snapcenter
    Verify if NetApp SnapCenter is installed. Look for the SnapCenter service or installation directory. On Windows, check services.msc for 'SnapCenter'; on Linux, check for the snapcenter service process.
    Affected if NetApp SnapCenter is present on the system (all versions are affected)

You are affected if MySQL Cluster version 8.0.0 through 8.0.28 is installed, OR any version of NetApp Active Iq Unified Manager, Oncommand Insight, or SnapCenter is present on the system.

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.28
Interim mitigation

Upgrade MySQL Cluster to a patched version (8.0.29 or later) and ensure physical security of the network infrastructure hosting the cluster. Restrict physical access to the communication segments and limit high-privilege access.

Recommended fix High confidence

MySQL Cluster 8.0.29 or later

  1. 1. Identify all MySQL Cluster installations in the environment running version 8.0.0 through 8.0.28
  2. 2. Review the NetApp product lifecycle advisories at security.netapp.com for specific patch guidance for Active IQ Unified Manager, OnCommand Insight, and SnapCenter if these products are in use
  3. 3. For standalone MySQL Cluster: plan an upgrade to MySQL Cluster 8.0.29 or later in a non-production environment first
  4. 4. Test the upgrade in a staging environment to verify application compatibility
  5. 5. Schedule a maintenance window and create a full backup of the MySQL Cluster data
  6. 6. Perform the upgrade following Oracle's official upgrade documentation for MySQL Cluster
  7. 7. Verify the MySQL Cluster services start successfully and all data is accessible
  8. 8. Confirm the upgrade by running: SELECT VERSION(); to verify the new version number
Caveat Review Oracle MySQL 8.0.29 release notes for any breaking changes or deprecated features before upgrading production systems

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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