LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). 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-2370 is a MySQL Server denial-of-service issue. An attacker already holding high privileges and network access could make MySQL hang or crash repeatedly. It does not indicate data theft or data modification, but it can interrupt applications that depend on affected MySQL versions.

Executive priority

Treat as a timely maintenance and resilience issue, not an emergency breach signal. Prioritize internet-reachable or business-critical MySQL services and environments with many privileged database users.

Technical view

Oracle describes this as a Server:DML vulnerability in MySQL Server 8.0.25 and prior. The CVSS 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 likely where MySQL Server 8.0.25 or earlier is reachable by privileged database users over the network. Embedded or packaged MySQL deployments may also matter, as shown by NetApp and Fedora advisories.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation. Practical abuse requires high privileges, so risk concentrates around compromised admin accounts, over-broad database privileges, or trusted users with network reachability.

Researcher notes

Evidence is limited to vendor and CVE references. No CWE is provided in the bundle, and no exploit details or fixed version beyond vendor CPU guidance are stated. Avoid assuming confidentiality or integrity impact.

Mitigation direction

  • Inventory MySQL Server 8.0.25 and earlier across servers, appliances, and packaged deployments.
  • Apply Oracle July 2021 CPU or later vendor-approved MySQL updates.
  • Check NetApp, Fedora, and other vendor advisories for embedded MySQL exposure.
  • Restrict privileged MySQL network access to trusted hosts and management networks.
  • Review database privilege assignments and remove unnecessary high-privilege accounts.

Validation and detection

  • Confirm exact MySQL versions and package sources on each database host.
  • Verify MySQL access controls limit privileged users to expected administrative sources.
  • Review database and service logs for repeated crashes, hangs, or unexpected restarts.
  • Confirm vendor update status for appliances or distributions bundling MySQL.
  • Document any accepted exceptions with compensating access controls.
Prepared
Confidence
high
Sources
6

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-2370 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
5Source 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-2370Attack 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.