LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: PS). 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-2422 is a denial-of-service issue in Oracle MySQL Server. An attacker already holding high privileges and network access can make affected MySQL servers hang or crash repeatedly, disrupting applications that depend on the database.

Executive priority

Treat this as a targeted availability risk, not a broad unauthenticated compromise. Prioritize remediation for production MySQL systems supporting revenue, operations, or customer-facing services, especially where privileged access is not tightly controlled.

Technical view

The issue affects MySQL Server 8.0.25 and prior, component Server: PS. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, scoring 4.9. Impact is availability only; the provided sources do not describe data theft, data modification, or privilege escalation.

Likely exposure

Exposure is mainly MySQL Server 8.0.25 and earlier instances reachable over the network by highly privileged users. Business risk increases where MySQL supports critical services, administrative access is broadly granted, or database network access is weakly segmented.

Exploitation context

The source bundle does not show known active exploitation, and the CVE is not marked KEV. Exploitation requires high privileges and network access, which reduces likelihood, but repeatable database crashes can still create meaningful outage risk.

Researcher notes

Provided sources identify affected versions, privileges, attack vector, and availability impact, but do not provide root cause details, proof-of-concept status, or vendor-specific workaround text. Avoid assuming exploitability beyond the stated high-privilege network scenario.

Mitigation direction

  • Apply Oracle MySQL security updates from the July 2021 Critical Patch Update guidance.
  • Upgrade affected MySQL Server deployments beyond 8.0.25 where applicable.
  • Restrict MySQL network access to trusted administration paths only.
  • Review high-privilege database accounts and remove unnecessary access.
  • Check NetApp guidance if MySQL is used with affected NetApp environments.

Validation and detection

  • Inventory MySQL Server versions and flag 8.0.25 or earlier.
  • Confirm Oracle July 2021 CPU fixes are applied.
  • Review network controls limiting access to MySQL services.
  • Audit high-privilege MySQL accounts for necessity and ownership.
  • Check database logs for unexplained hangs, crashes, or repeated restarts.
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-2422 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-2422Attack 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.