LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2779: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 8.0.18 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

This MySQL Server flaw can let an already highly privileged user reach the database over the network and make it hang or repeatedly crash. The main business impact is service availability, not data theft or data alteration based on the supplied CVSS vector.

Executive priority

Handle as a scheduled but real availability risk. Escalate priority for business-critical databases, broadly reachable MySQL services, or environments with many administrators. The sources support denial-of-service impact, not confidentiality or integrity compromise.

Technical view

CVE-2020-2779 affects Oracle MySQL Server 8.0.18 and prior in the Server: Security: Privileges component. It is network-accessible, low-complexity, requires high privileges, and has no user interaction. Successful exploitation can cause complete denial of service through hangs or repeatable crashes.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.18 or earlier is reachable over allowed network protocols and high-privileged database accounts exist. Systems using vendor-packaged MySQL should also check Oracle, NetApp, Fedora, and Gentoo advisories for applicability.

Exploitation context

The supplied sources do not show CISA KEV listing or confirmed active exploitation. Exploitation requires high privileges, which lowers broad internet risk, but an insider, compromised administrator account, or chained access path could turn it into a meaningful outage risk.

Researcher notes

The source bundle identifies the affected component and CVSS vector but does not include root-cause details, proof-of-concept material, or exact fixed versions. Avoid assuming exploit availability. Validation should focus on version, privilege model, network reachability, and vendor advisory coverage.

Mitigation direction

  • Identify MySQL Server instances running 8.0.18 or earlier.
  • Apply Oracle CPU or distribution vendor remediation guidance for affected MySQL packages.
  • Restrict network access to MySQL services to trusted hosts only.
  • Reduce and review high-privileged MySQL accounts.
  • Monitor database crashes, hangs, and repeated availability failures.

Validation and detection

  • Confirm deployed MySQL Server versions across production and managed appliances.
  • Review Oracle April 2020 CPU applicability for each instance.
  • Check vendor advisories for NetApp, Fedora, or Gentoo packaged deployments.
  • Verify MySQL network exposure and firewall allowlists.
  • Audit high-privileged MySQL users and recent privileged activity.
Prepared
Confidence
high
Sources
8

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-2779 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
7Source 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-2779Attack 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.18 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.