LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.23 and prior. Easily exploitable vulnerability allows low 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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 6.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-2172 is a denial-of-service flaw in Oracle MySQL Server. A low-privileged user who can reach MySQL over the network may cause the server to hang or crash repeatedly, disrupting applications that depend on that database.

Executive priority

Treat this as a moderate availability risk. Prioritize internet-adjacent, shared, or business-critical MySQL deployments because a crash loop could interrupt dependent services, even though the sources do not indicate data compromise or active exploitation.

Technical view

Oracle describes this as a MySQL Server DML component vulnerability affecting supported MySQL Server versions 8.0.23 and prior. The CVSS vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, indicating network reachability, low attack complexity, required low privilege, and high availability impact only.

Likely exposure

Exposure is most relevant for MySQL Server 8.0.23 and earlier, especially where many application, partner, or user accounts have database access over network protocols. Fedora and NetApp advisories indicate downstream ecosystem tracking, but exact product impact should be verified with those vendors.

Exploitation context

The supplied sources do not cite active exploitation, and the CVE is not marked as KEV. Risk comes from easy network exploitation by an authenticated low-privileged attacker, with the impact limited to database availability rather than data theft or modification.

Researcher notes

Key constraints are PR:L and availability-only impact. The source bundle does not provide root-cause detail, proof-of-concept information, or exact fixed version. Avoid assuming broader MySQL variants, unauthenticated exposure, or exploitation in the wild without additional vendor evidence.

Mitigation direction

  • Apply Oracle, Fedora, or relevant vendor security updates after confirming affected inventory.
  • Check NetApp guidance if MySQL is embedded in supported NetApp products or appliances.
  • Restrict network access to MySQL to trusted application hosts and administrators.
  • Review and remove unnecessary low-privileged MySQL accounts.
  • Monitor database availability until affected systems are updated.

Validation and detection

  • Inventory MySQL Server instances and identify versions 8.0.23 or earlier.
  • Confirm whether affected systems are reachable over network protocols.
  • Map low-privileged accounts that can authenticate to each MySQL instance.
  • Check vendor advisories for the applicable fixed package or product status.
  • Review logs and monitoring for unexplained MySQL hangs or repeatable crashes.
Prepared
Confidence
high
Sources
7

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-2172 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
6Source 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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-2172Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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.23 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.