LiveActive security incident?Get immediate response
CVE Record

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

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 5.7.31 and prior and 8.0.21 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-2020-14776 is a MySQL Server availability issue in InnoDB. A highly privileged network attacker could make affected MySQL instances hang or repeatedly crash. It does not describe data theft or data modification, but database downtime can disrupt applications that depend on MySQL.

Executive priority

Treat this as a planned remediation item unless the affected database is business-critical, externally reachable, or broadly accessible by privileged users. Prioritize patching where downtime would affect revenue, customer operations, or core internal systems.

Technical view

Oracle lists affected MySQL Server versions as 5.7.31 and prior, and 8.0.21 and prior. The CVSS 3.1 score is 4.9, with network attack vector, low complexity, high privileges required, no user interaction, and high availability impact only.

Likely exposure

Exposure is most relevant where affected MySQL versions are reachable over the network by users or services with high database privileges. Internet exposure increases operational risk, but the attacker still needs high privileges according to the CVSS vector.

Exploitation context

The provided bundle does not show CISA KEV listing or evidence of active exploitation. The issue is described as easily exploitable after high-privilege access is present, with impact limited to denial of service.

Researcher notes

Evidence points to an InnoDB denial-of-service flaw requiring high privileges over network protocols. The public bundle does not include CWE, root-cause detail, exploit primitives, or specific fixed Oracle version numbers beyond the affected version boundaries.

Mitigation direction

  • Apply Oracle CPU guidance or vendor packages addressing CVE-2020-14776.
  • Upgrade MySQL beyond affected 5.7.31 and 8.0.21 baselines where applicable.
  • Restrict MySQL network access to trusted application and administration paths.
  • Review and reduce high-privilege MySQL accounts.
  • Monitor MySQL crashes, hangs, and abnormal restart loops.

Validation and detection

  • Inventory all MySQL Server versions and identify 5.7.31, 8.0.21, or earlier.
  • Confirm vendor package advisories include CVE-2020-14776 fixes.
  • Check whether MySQL ports are reachable beyond approved networks.
  • Review privileged database accounts and service credentials.
  • Inspect MySQL and service manager logs for repeated crashes or hangs.
Prepared
Confidence
high
Sources
5

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-14776 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
10Source 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-2020-14776Attack 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.31 and prior, 8.0.21 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.