LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2299: 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
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-2299 can let a highly privileged network user crash or hang MySQL Server. The business impact is service outage, not data theft or data modification based on the provided CVSS and description.

Executive priority

Treat as a moderate reliability risk. Prioritize internet-reachable or business-critical MySQL systems, especially where many users or applications hold high database privileges.

Technical view

Oracle describes a MySQL Server Optimizer flaw affecting supported versions 8.0.23 and prior. It is network-reachable, low complexity, requires high privileges, and can cause complete denial of service. CVSS is 4.9 with availability-only impact.

Likely exposure

Exposure is most likely where Oracle MySQL Server 8.0.23 or earlier is reachable by privileged database users over network protocols.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires high privileges, reducing broad attack likelihood, but insider or compromised-admin scenarios could still disrupt service.

Researcher notes

Focus on version confirmation, privilege model, and network reachability. The source bundle identifies DoS impact but does not provide exploit details, CWE mapping, or a named fixed version.

Mitigation direction

  • Inventory MySQL Server instances and identify versions 8.0.23 or earlier.
  • Review Oracle April 2021 CPU guidance for the applicable fixed or supported release.
  • Limit MySQL network access to trusted administrative and application sources.
  • Review and reduce high-privilege MySQL accounts where operationally possible.
  • Monitor database availability and crash patterns on affected servers.

Validation and detection

  • Confirm running MySQL Server versions across production and managed appliances.
  • Check whether Oracle April 2021 CPU remediation has been applied.
  • Validate that high-privilege database accounts are limited and justified.
  • Confirm MySQL network exposure is restricted by firewall or security group policy.
  • Review logs for unexplained hangs, crashes, or repeated service restarts.
Prepared
Confidence
medium
Sources
4

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-2299 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-2299Attack 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.