LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Logging). 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

CVE-2020-2770 is a MySQL Server denial-of-service issue in the logging component. An already high-privileged attacker with network access can cause MySQL Server to hang or crash repeatedly. This is not described as data theft or privilege escalation, but database availability disruption can affect applications relying on MySQL.

Executive priority

Treat as a scheduled but real availability risk. It is not marked as actively exploited and requires high privileges, but affected business-critical MySQL systems should be upgraded because successful abuse can repeatedly crash the database service.

Technical view

Oracle reports affected MySQL Server versions are 8.0.18 and prior. The CVSS vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, meaning network reachable, low complexity, high privileges required, and availability-only impact. The source bundle lists no CWE and no exploit procedure.

Likely exposure

Exposure is most likely where MySQL Server 8.0.18 or earlier is reachable over allowed database protocols by privileged users, services, or administrators. Systems using vendor-packaged MySQL from Fedora, Gentoo, NetApp-affected environments, or Oracle upstream should be checked against their advisory status.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. Exploitation requires high privileges, which lowers likelihood, but the network attack vector and repeatable complete denial of service make it operationally relevant for critical databases.

Researcher notes

Focus review on MySQL Server logging behavior only as described by Oracle. The provided sources do not name a CWE, proof of exploitation, or detailed root cause. Avoid broadening scope to other MySQL branches, forks, or products without vendor confirmation.

Mitigation direction

  • Identify MySQL Server instances running 8.0.18 or earlier.
  • Apply Oracle, Fedora, Gentoo, or NetApp fixed packages where applicable.
  • Restrict MySQL network access to required trusted hosts only.
  • Review and reduce high-privileged MySQL accounts where possible.
  • Check vendor advisories before assuming a specific fixed version.

Validation and detection

  • Inventory MySQL Server versions across production and backup environments.
  • Confirm whether any instance is 8.0.18 or earlier.
  • Verify database ports are not exposed beyond approved networks.
  • Review service monitoring for unexplained MySQL hangs, crashes, or restarts.
  • Confirm package remediation status against relevant vendor advisories.
Prepared
Confidence
medium
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-2770 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-2770Attack 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.