LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35602: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Options).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Options). Supported versions that are affected are 8.0.26 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.0 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H).

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-35602 affects Oracle MySQL Server 8.0.26 and earlier. A highly privileged network attacker could crash the database service repeatedly or modify some accessible data. This is not a broad unauthenticated takeover, but it matters where MySQL availability or data integrity supports critical business processes.

Executive priority

Treat as a scheduled remediation item unless exposed privileged access or critical MySQL workloads raise business impact. Prioritize databases supporting revenue, operations, or regulated data because the main risk is outage and limited data tampering.

Technical view

The issue is in MySQL Server's Server: Options component. CVSS 3.1 is 5.0: network reachable, high complexity, high privileges required, no user interaction, unchanged scope, no confidentiality impact, low integrity impact, and high availability impact.

Likely exposure

Exposure is limited to MySQL Server deployments running 8.0.26 or earlier, including downstream packaged versions referenced by Fedora and NetApp advisories. Risk is higher where privileged database accounts are network-accessible across multiple protocols.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not marked KEV. Exploitation requires high privileges and high attack complexity, but successful attacks may cause complete denial of service and limited unauthorized data modification.

Researcher notes

The bundle does not provide CWE details, root-cause mechanics, exploit proof, or exact fixed version text. Analysis should stay anchored to Oracle's advisory and downstream vendor updates rather than assuming exploitability beyond the CVSS vector and CVE description.

Mitigation direction

  • Identify MySQL Server instances running 8.0.26 or earlier.
  • Review Oracle October 2021 CPU guidance for applicable MySQL updates.
  • Check downstream vendor advisories for packaged MySQL or affected appliances.
  • Restrict network access to MySQL from trusted administrative paths only.
  • Review privileged database accounts and remove unnecessary access.

Validation and detection

  • Inventory MySQL Server versions across hosts, containers, and managed images.
  • Confirm whether any instance reports version 8.0.26 or earlier.
  • Check vendor package changelogs against Oracle CPU October 2021 references.
  • Verify MySQL ports are not broadly reachable from untrusted networks.
  • Review logs for unexplained MySQL hangs or repeated crashes.
Prepared
Confidence
high
Sources
7

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-35602 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
5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/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
6Source 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
5CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H0.74.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/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 Server8.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.