LiveActive security incident?Get immediate response
CVE Record

CVE-2022-21525: 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.29 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-2022-21525 is a MySQL Server denial-of-service issue. A high-privileged user who can reach MySQL over the network may trigger a hang or repeatable crash. The business impact is database unavailability, not data theft or tampering, based on the provided sources.

Executive priority

Treat as a moderate availability risk. Prioritize business-critical databases, externally reachable systems, and environments with broad privileged database access. It is less urgent than unauthenticated remote code execution or data exposure flaws.

Technical view

Oracle describes the flaw in MySQL Server's Server: Optimizer component, affecting supported versions 8.0.29 and prior. CVSS 3.1 is 4.9: network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most likely where MySQL Server 8.0.29 or earlier remains deployed and accessible to privileged database users over supported network protocols. Internet exposure increases operational risk, but the source requires high privileges.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation is described as easy once the attacker already has high privileges and network access, with the expected outcome limited to service hang or crash.

Researcher notes

No CWE is provided in the bundle. The sources identify availability-only impact and high-privilege preconditions. The bundle does not name a specific fixed MySQL release, so remediation should follow Oracle and downstream vendor advisories rather than inferred version assumptions.

Mitigation direction

  • Apply Oracle July 2022 CPU guidance or later vendor-provided MySQL updates.
  • Upgrade affected MySQL Server 8.0.29 and prior deployments according to vendor guidance.
  • Restrict network access to MySQL from only trusted administrative and application sources.
  • Review and minimize high-privileged MySQL accounts.
  • Check downstream vendor advisories for packaged or appliance-managed MySQL instances.

Validation and detection

  • Inventory MySQL Server versions and flag 8.0.29 or prior.
  • Confirm package or appliance status against Oracle, Fedora, or NetApp guidance as applicable.
  • Verify MySQL is not reachable from untrusted networks.
  • Review privileged database accounts for unnecessary grants or stale users.
  • Check service monitoring for unexplained MySQL hangs or repeated crashes.
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-2022-21525 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-2022-21525Attack 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.29 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.