LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2160: 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 5.7.30 and prior and 8.0.17 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-2160 is a denial-of-service flaw in Oracle MySQL Server. A highly privileged attacker with network access could make MySQL hang or crash repeatedly, disrupting applications that depend on the database. The sources do not show data theft, data alteration, or active exploitation.

Executive priority

Treat as a moderate operational resilience issue. Prioritize databases supporting business-critical services, especially where privileged access is widely distributed or exposed over networks. It is not presented as a data breach vulnerability in the provided sources.

Technical view

The issue affects MySQL Server Optimizer in versions 5.7.30 and prior, and 8.0.17 and prior. CVSS 3.1 is 4.9: network exploitable, low complexity, high privileges required, no user interaction, availability-only impact with complete DoS possible.

Likely exposure

Exposure is most likely where affected MySQL versions are still running and privileged database accounts can connect over network protocols. Internet-reachable or broadly accessible administrative database paths raise operational risk, but high privileges are required.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The practical concern is service disruption by a privileged user or an attacker who has already obtained privileged MySQL access.

Researcher notes

Key limits are PR:H and availability-only impact. The provided bundle does not include exploit details, CWE mapping, or exact fixed version numbers. Avoid assuming active exploitation or downstream affected products beyond cited Oracle MySQL and referenced vendor advisories.

Mitigation direction

  • Identify MySQL Server instances at or below 5.7.30 and 8.0.17.
  • Review Oracle April 2021 CPU guidance for supported fixed releases.
  • Apply vendor-supported MySQL updates where applicable.
  • Restrict privileged MySQL access to trusted administrative networks.
  • Review NetApp guidance if MySQL is embedded in supported NetApp products.

Validation and detection

  • Inventory MySQL Server versions across production and backup environments.
  • Confirm affected instances are upgraded or covered by vendor guidance.
  • Audit privileged MySQL accounts and network access paths.
  • Check monitoring for repeated MySQL hangs, crashes, or unexplained restarts.
  • Verify dependency owners understand availability-only impact and service risk.
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-2160 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-2160Attack 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 Server5.7.30 and prior, 8.0.17 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.