LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2930: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Parser).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Parser). Supported versions that are affected are 8.0.19 and prior. Difficult to exploit 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.4 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

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

Security readout for executives and security teams

Plain-English summary

CVE-2020-2930 is an Oracle MySQL Server parser flaw that can let a highly privileged network attacker crash or hang the database. It does not indicate data theft or data modification, but successful exploitation can cause complete denial of service for affected MySQL instances.

Executive priority

Treat this as a medium-priority availability issue. It is unlikely to be the first emergency unless the affected database supports critical services, remains unpatched, or privileged access is broadly available.

Technical view

Oracle lists affected MySQL Server versions as 8.0.19 and prior. The CVSS 3.0 vector is AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H, meaning network-reachable, high-complexity exploitation requiring high privileges, with availability-only impact.

Likely exposure

Exposure is most likely where MySQL Server 8.0.19 or earlier remains deployed, including vendor-packaged distributions referenced by Ubuntu, Fedora, Gentoo, and NetApp advisories. Risk increases when privileged MySQL access is available over a network.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. The vulnerability is described as difficult to exploit and requiring high privileges, so insider, compromised admin, or chained-access scenarios are the primary concern.

Researcher notes

The source bundle identifies the component as Server: Parser but does not provide root-cause detail, proof-of-concept status, or fixed version specifics beyond affected versions. Avoid assuming exploitability beyond Oracle's high-privilege, high-complexity network scenario.

Mitigation direction

  • Apply Oracle April 2020 CPU or later MySQL Server security updates.
  • Update affected Ubuntu, Fedora, Gentoo, or NetApp-provided packages per vendor advisories.
  • Retire or isolate MySQL Server 8.0.19 and prior where updates are unavailable.
  • Restrict network access to MySQL services to trusted systems only.
  • Review and reduce high-privilege MySQL accounts where operationally possible.

Validation and detection

  • Inventory MySQL Server versions and flag 8.0.19 or earlier.
  • Confirm installed packages include vendor security updates for this CVE.
  • Check whether MySQL network services are reachable from untrusted networks.
  • Review privileged MySQL accounts and recent authentication activity.
  • Monitor database logs and availability tooling for unexplained hangs or crashes.
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-2930 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.4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:H/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.4CVSS 3.0MediumCVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H0.73.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

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

Vector: CVSS:3.0/AV:N/AC:H/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.