LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2425: 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.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-2425 can let a highly privileged network user crash or hang MySQL Server, causing a full service outage. It does not indicate data theft or data modification. Business urgency depends on whether older MySQL 8.0 deployments exist and whether powerful database accounts can connect remotely.

Executive priority

Treat this as a targeted availability risk, not a broad data breach signal. Prioritize patching internet-reachable or business-critical MySQL systems, then reduce privileged remote access.

Technical view

The issue affects Oracle MySQL Server 8.0.25 and prior, in the Server: Optimizer component. The CVSS 3.1 score is 4.9 with network attack vector, low complexity, high privileges required, no user interaction, and high availability impact only.

Likely exposure

Exposure is most likely where MySQL Server 8.0.25 or earlier remains deployed and high-privileged accounts have network access. Publicly exposed administrative access, shared privileged accounts, or weak segmentation would increase operational risk.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The vulnerability is described as easily exploitable, but only by a high-privileged attacker with network access via multiple protocols.

Researcher notes

Evidence is limited to vendor and CVE records. No CWE is provided, and no exploit details or confirmed exploitation are cited. Validation should focus on version exposure, privilege boundaries, and outage telemetry rather than reproducing crashes.

Mitigation direction

  • Identify all MySQL Server 8.0.25 and earlier deployments.
  • Review Oracle July 2021 CPU guidance and apply supported vendor updates.
  • Restrict network access to MySQL from trusted application and administration paths.
  • Audit high-privileged MySQL accounts and remove unnecessary remote access.
  • Check NetApp advisory relevance where NetApp products embed or depend on MySQL.

Validation and detection

  • Confirm MySQL Server versions across production, staging, and backup environments.
  • Verify database accounts with high privileges and network login capability.
  • Review MySQL availability incidents for unexplained hangs or repeatable crashes.
  • Confirm patch status against Oracle July 2021 CPU guidance.
  • Document any compensating controls for systems awaiting update.
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-2425 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-2425Attack 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.