LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are 8.0.25 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-2399 is a MySQL Server availability flaw. An already high-privileged user who can reach the server over the network may make MySQL hang or crash repeatedly. It is not described as data theft or privilege escalation, but it can disrupt databases supporting business services.

Executive priority

Treat this as a reliability and continuity issue, not a breach indicator from the provided evidence. Prioritize systems where MySQL supports critical services and privileged access is broad.

Technical view

Oracle describes the vulnerable component as Server: DDL in MySQL Server 8.0.25 and prior. CVSS 3.1 is 4.9: network reachable, low complexity, no user interaction, high privileges required, high availability impact, and no confidentiality or integrity impact.

Likely exposure

Exposure is most likely where MySQL Server 8.0.25 or earlier remains reachable by privileged database users or administrative service accounts over network protocols.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Exploitation requires high privileges, so risk centers on malicious insiders, compromised admin accounts, or over-privileged applications.

Researcher notes

The record lacks CWE detail and exploit specifics. Keep analysis bounded to Oracle’s DDL component description, affected versions, CVSS vector, and availability-only impact unless additional vendor evidence is reviewed.

Mitigation direction

  • Review Oracle July 2021 CPU guidance for the applicable MySQL Server update.
  • Upgrade affected MySQL Server versions according to vendor-supported guidance.
  • Restrict MySQL network access to trusted systems and administrative paths.
  • Review high-privilege database accounts and remove unnecessary access.
  • Monitor MySQL crashes, hangs, and repeated service restarts.

Validation and detection

  • Inventory MySQL Server instances and identify versions 8.0.25 and prior.
  • Confirm whether Oracle July 2021 CPU guidance has been applied.
  • Verify privileged MySQL accounts are required, owned, and monitored.
  • Check database exposure across internal networks and management interfaces.
  • Review uptime and error logs for repeated 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-2399 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-2399Attack 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.25 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.