LiveActive security incident?Get immediate response
CVE Record

CVE-2022-21537: Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). 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

This MySQL Server flaw can let a highly privileged network attacker crash or hang the database. The stated business risk is service outage, not data theft or tampering. Systems running MySQL Server 8.0.29 or earlier are the focus.

Executive priority

Treat this as a moderate availability risk for business systems dependent on MySQL. Prioritize externally reachable, production, and mission-critical databases, especially where privileged accounts are widely distributed.

Technical view

CVE-2022-21537 affects Oracle MySQL Server InnoDB in supported versions 8.0.29 and prior. It is network reachable, low complexity, requires high privileges, needs no user interaction, and has high availability impact only. CVSS is 4.9.

Likely exposure

Exposure is most likely where MySQL Server 8.0.29 or earlier is reachable by privileged accounts over network protocols. Public exposure increases operational risk, but the CVSS privileges requirement limits attacker reach.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. Oracle describes the issue as easily exploitable by a high privileged attacker with network access, causing a hang or repeatable crash.

Researcher notes

The public description identifies InnoDB but does not include root cause, exploit mechanics, or a CWE. Avoid assuming broader impact beyond complete denial of service. Validation should focus on version, vendor packaging, network reachability, and privileged-account exposure.

Mitigation direction

  • Inventory MySQL Server deployments and flag supported 8.0.29 and earlier versions.
  • Review Oracle July 2022 CPU guidance and apply vendor-supported MySQL updates.
  • Check NetApp guidance if affected products bundle or depend on MySQL components.
  • Apply relevant Fedora package updates where Fedora-provided MySQL packages are used.
  • Restrict MySQL network access to trusted administrative and application sources.

Validation and detection

  • Confirm each MySQL Server version and compare it against 8.0.29 and earlier.
  • Verify update status against Oracle, NetApp, or Fedora advisory guidance as applicable.
  • Review firewall and security group rules for unnecessary MySQL network exposure.
  • Confirm privileged database accounts are limited, current, and assigned to valid owners.
  • Monitor MySQL availability logs for unexplained hangs, crashes, or repeated restarts.
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-21537 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-21537Attack 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.