LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35623: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Roles).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Roles). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).

LowCVSS 2.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Oracle MySQL Server flaw can let an already highly privileged network attacker read a limited subset of database-accessible data. It is not described as unauthenticated or broadly destructive. Business urgency is mainly for environments where MySQL administrative access is shared, exposed, or poorly monitored.

Executive priority

Handle through normal patch governance, with faster action for internet-reachable, shared-administration, or compliance-sensitive database environments. The main business risk is limited unauthorized data read by someone already holding substantial privileges.

Technical view

CVE-2021-35623 affects Oracle MySQL Server 8.0.26 and prior in the Security: Roles component. The CVSS 3.1 score is 2.7: network exploitable, low complexity, high privileges required, no user interaction, confidentiality impact only.

Likely exposure

Exposure is limited to supported Oracle MySQL Server deployments at 8.0.26 or earlier where high-privileged users can connect over MySQL-supported network protocols.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit availability, or detailed attack mechanics. The vulnerability requires high privileges, which reduces broad external risk but still matters for insider, compromised-admin, and delegated-access scenarios.

Researcher notes

Evidence is sparse: no CWE is listed, no exploit details are provided, and no active exploitation is cited. Assessment should focus on version exposure, privilege boundaries, role configuration, and whether compensating network controls reduce reachable attack surface.

Mitigation direction

  • Apply the relevant Oracle October 2021 Critical Patch Update guidance.
  • Upgrade MySQL Server beyond affected 8.0.26-and-prior versions where applicable.
  • Restrict network access to MySQL administrative interfaces.
  • Review high-privileged MySQL accounts and remove unnecessary role grants.
  • Check NetApp advisory applicability if NetApp products depend on MySQL exposure.

Validation and detection

  • Inventory Oracle MySQL Server versions across production and managed environments.
  • Flag any MySQL Server instance running 8.0.26 or earlier.
  • Confirm Oracle CPU or vendor-supported update status.
  • Review privileged MySQL accounts with network login capability.
  • Verify database access is restricted to approved hosts and administrators.
Prepared
Confidence
high
Sources
4

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-35623 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
Low
CVSS
2.7 (3.1)
Known Exploited
No
Published

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

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
3Source 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
2.7CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N1.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.7Low
CVSS 3.1 vector shape for CVE-2021-35623Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.