LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2901: 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.19 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.0 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.0/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-2020-2901 can let a highly privileged remote MySQL user crash or hang MySQL Server. It does not indicate data theft or data modification, but it can disrupt applications that rely on affected MySQL versions.

Executive priority

Treat as a moderate operational availability issue. Prioritize internet- or broadly network-reachable MySQL servers and environments with many privileged database users, especially where application downtime has business impact.

Technical view

Oracle describes a MySQL Server Optimizer vulnerability affecting versions 8.0.19 and prior. A high-privileged attacker with network access over multiple protocols can cause a hang or frequently repeatable crash, producing complete denial of service. CVSS 3.0 is 4.9 with high availability impact only.

Likely exposure

Exposure is most likely where MySQL Server 8.0.19 or earlier remains deployed and reachable by users or services holding high-privileged database credentials. Distribution-packaged MySQL deployments should be checked against Ubuntu, Fedora, Gentoo, and other vendor advisories.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires high privileges and network access, so business risk depends heavily on administrative credential control and database network exposure.

Researcher notes

The public description is limited to component, privilege requirement, impact, and affected versions. No CWE, proof-of-concept, root cause, or exploit details are provided in the bundle, so validation should focus on version exposure and vendor patch status.

Mitigation direction

  • Inventory MySQL Server instances and identify versions 8.0.19 or earlier.
  • Apply Oracle April 2020 CPU updates or corresponding distribution security packages.
  • Restrict MySQL network access to trusted administrative hosts and application networks.
  • Review and reduce high-privileged MySQL accounts where operationally possible.
  • Monitor MySQL crashes, restarts, and availability alerts until remediation is complete.

Validation and detection

  • Confirm each MySQL Server version and package source against vendor advisories.
  • Verify patched systems no longer report affected 8.0.19-or-prior builds.
  • Review firewall, security group, and bind-address exposure for MySQL services.
  • Audit high-privileged MySQL accounts and recent administrative login activity.
  • Check database logs for unexplained optimizer-related crashes or repeated restarts.
Prepared
Confidence
high
Sources
9

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-2020-2901 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.0)
Known Exploited
No
Published

Vector: CVSS:3.0/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
8Source 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.0MediumCVSS:3.0/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.0 score

4.9Medium
CVSS 3.0 vector shape for CVE-2020-2901Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/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.19 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.