LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Locking). 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-2402 is a denial-of-service flaw in Oracle MySQL Server. A high-privileged attacker with network access can make affected MySQL servers hang or crash repeatedly. It does not indicate data theft or data modification, but it can disrupt business systems that depend on MySQL availability.

Executive priority

Treat this as a moderate availability risk. Prioritize remediation for business-critical databases and environments where many privileged users or service accounts can access MySQL remotely.

Technical view

The flaw affects MySQL Server 8.0.25 and prior in the Server: Locking component. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, reflecting network reachability, low attack complexity, required high privileges, and complete availability impact.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.25 or earlier is deployed and reachable over the network by highly privileged database users, administrators, applications, or service accounts.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. Practical risk depends on whether a high-privileged network-accessible account can reach the affected MySQL service.

Researcher notes

No CWE is provided in the source bundle. The vulnerability is limited to availability impact in the cited CVSS vector. The sources do not provide exploit details, indicators of compromise, or a standalone mitigation beyond vendor advisory review and updating.

Mitigation direction

  • Identify all MySQL Server instances at version 8.0.25 or earlier.
  • Review Oracle July 2021 CPU guidance for the applicable MySQL update path.
  • Upgrade affected MySQL Server deployments to a vendor-supported fixed release.
  • Restrict privileged MySQL access to trusted administration paths and service accounts.
  • Review NetApp advisory if MySQL is embedded or bundled in NetApp-managed environments.

Validation and detection

  • Confirm MySQL Server versions across production, staging, and backup environments.
  • Check whether privileged accounts can reach MySQL over network paths.
  • Review database crash, hang, and restart logs for unexplained availability events.
  • Verify Oracle CPU remediation is applied according to vendor guidance.
  • Document any accepted risk for unsupported or deferred-upgrade systems.
Prepared
Confidence
medium
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-2402 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-2402Attack 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.