CVE Tools

CVE-2021-35621

Exploitation likely. EPSS gives it a 50% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Oracle Corporation MySQL ClusterAffected: 7.4.33 and priorUpgrade to: not statedAffected: 7.5.23 and priorUpgrade to: not statedAffected: 7.6.19 and priorUpgrade to: not statedAffected: 8.0.26 and priorUpgrade to: not statedStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether you run MySQL Cluster and identify its installed version.
  2. If it is 7.4.33 or earlier, 7.5.23 or earlier, 7.6.19 or earlier, or 8.0.26 or earlier, review Oracle's October 2021 security advisory for the applicable update.
  3. Schedule the vendor-provided MySQL Cluster update after testing it in a non-production environment.
  4. Restrict access to the network segment used by the cluster to authorized administrators and systems only.

What it is

From the CVE record

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.33 and prior, 7.5.23 and prior, 7.6.19 and prior and 8.0.26 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).

In plain language

Written by AI from the record

MySQL Cluster versions 7.4.33 and earlier, 7.5.23 and earlier, 7.6.19 and earlier, and 8.0.26 and earlier have a flaw, but a typical small business is unlikely to face immediate risk.

A difficult-to-exploit MySQL Cluster vulnerability requires a highly privileged attacker on the attached physical network segment and interaction by another person, potentially resulting in full cluster compromise.

If you're affected

  • Full cluster takeover
  • Database data exposure
  • Database data changes
  • Service disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

50% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 1790 days, from the signal feeds we watch.

  1. EPSS band changemoderate → highepss band change
  2. OpenVAS check added
  3. EPSS band changelow → moderate
  4. Patch availablerecord updated
  5. Publishedweakness classified

Affected products

Technical detail

CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H

Scored 6.3 by NVD.

How it is reached

  • Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required HighRequires admin or elevated privileges
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Netapp, not every advisory.