LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.23 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 ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

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

Security readout for executives and security teams

Plain-English summary

CVE-2021-2230 is an Oracle MySQL Server availability flaw in the Server Optimizer. An already high-privileged network user could make MySQL hang or crash repeatedly, causing database downtime. The issue is not described as data theft or privilege escalation.

Executive priority

Treat as a patching and resilience priority for production databases still on affected MySQL versions. Urgency is lower than unauthenticated remote code execution, but downtime impact can be material where privileged access is broad or poorly monitored.

Technical view

Oracle lists affected MySQL Server versions as 8.0.23 and prior. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, meaning network reachable, low complexity, high privileges required, and availability-only impact.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.23 or earlier remains deployed and reachable by privileged database users over supported network protocols. Appliances or managed products embedding MySQL should be checked against their vendor advisories.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked KEV. Exploitation requires high privileges, which reduces broad external risk, but a compromised privileged account could still cause complete database denial of service.

Researcher notes

The public record identifies the vulnerable component as Server: Optimizer and gives no CWE or root-cause detail. Do not assume confidentiality or integrity impact. Focus validation on version exposure, privilege boundaries, network reachability, and vendor patch status.

Mitigation direction

  • Inventory MySQL Server versions and identify any 8.0.23 or earlier deployments.
  • Apply Oracle CPU guidance or upgrade to a vendor-supported fixed release.
  • Restrict MySQL network access to trusted administrative and application paths.
  • Review high-privilege MySQL accounts and remove unnecessary privileges.
  • Check third-party vendor advisories for embedded MySQL exposure.

Validation and detection

  • Confirm running MySQL versions against Oracle affected-version guidance.
  • Verify Oracle April 2021 CPU remediation status in patch records.
  • Review database access paths for unnecessary network exposure.
  • Audit privileged MySQL accounts for unused or excessive access.
  • Check monitoring for repeated MySQL crashes or hangs.
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-2230 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
4.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/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
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
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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