LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35593: Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General).

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

MediumCVSS 6.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-35593 affects Oracle MySQL Cluster. A highly privileged attacker already on the cluster’s physical communication segment, and requiring another user’s interaction, could take over the cluster. This is not a typical internet-facing issue, but the business impact is high where affected clusters support critical data services.

Executive priority

Prioritize remediation for production or mission-critical MySQL Cluster environments, especially where segmentation is weak. The exploitation bar is high, but successful compromise could mean full cluster takeover and major data-service impact.

Technical view

Oracle lists affected MySQL Cluster versions as 7.4.33 and prior, 7.5.23 and prior, 7.6.19 and prior, and 8.0.26 and prior. CVSS 3.1 is 6.3 with adjacent access, high complexity, high privileges, and user interaction required, but successful exploitation can affect confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to organizations running affected MySQL Cluster versions on internal or segmented infrastructure. Risk increases where cluster communication networks are shared, weakly segmented, or accessible by privileged administrators beyond the database operations team.

Exploitation context

The provided sources do not show active exploitation, and CISA KEV status is false. Exploitation is described as difficult, requiring high privileges, access to the physical communication segment, and human interaction from another person.

Researcher notes

The public description gives impact and preconditions but not root cause detail, exploit technique, or fixed version mapping beyond Oracle CPU context. Avoid assuming remote exploitability or public weaponization from the provided evidence.

Mitigation direction

  • Apply Oracle October 2021 CPU or later supported MySQL Cluster security updates.
  • Identify and upgrade affected MySQL Cluster versions listed by Oracle.
  • Restrict access to the cluster communication segment to required systems and administrators.
  • Review NetApp advisory applicability if MySQL Cluster is embedded or supported through NetApp products.
  • Monitor vendor guidance for version-specific remediation details.

Validation and detection

  • Inventory MySQL Cluster deployments and record exact version numbers.
  • Confirm whether any deployment is 7.4.33, 7.5.23, 7.6.19, 8.0.26, or earlier.
  • Validate network segmentation around the cluster physical communication segment.
  • Check change records for Oracle CPU October 2021 or later remediation.
  • Review access lists for privileged accounts with cluster network reachability.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-35593 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.3CVSS 3.1MediumCVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H0.45.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2021-35593Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Cluster7.4.33 and prior, 7.5.23 and prior, 7.6.19 and prior, 8.0.26 and priorListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.