LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2895: 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 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-2895 is a MySQL Server InnoDB flaw that can let a highly privileged network attacker crash or hang the database. The impact is service availability, not data theft or tampering in the provided sources. Systems running MySQL Server 8.0.19 or earlier should be treated as exposed until vendor updates are confirmed.

Executive priority

Prioritize remediation for internet-adjacent, business-critical, or single-node MySQL services. The issue is not rated critical because high privileges are required, but a successful attack can still cause database downtime and application disruption.

Technical view

Oracle describes an easily exploitable MySQL Server InnoDB vulnerability affecting supported versions 8.0.19 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 complete availability impact only.

Likely exposure

Exposure is most likely where MySQL Server 8.0.19 or earlier is reachable over the network by privileged database users or administrators. Business risk is higher for production systems without clustering, failover, or rapid database restart capability.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires high privileges and network access, so the main scenarios are malicious insiders, compromised privileged database credentials, or over-permissive administrative access paths.

Researcher notes

The public details identify InnoDB, availability-only impact, affected versions, and CVSS scoring. The bundle does not provide a CWE, root-cause details, exploit status, or precise fixed build numbers, so validation should rely on Oracle and distribution advisories.

Mitigation direction

  • Apply Oracle April 2020 CPU guidance or relevant OS vendor MySQL packages.
  • Confirm MySQL Server is upgraded beyond affected 8.0.19 and prior versions.
  • Restrict MySQL network access to trusted hosts and administrative paths.
  • Review privileged MySQL accounts and remove unnecessary elevated access.
  • Monitor database crashes, hangs, and repeated restart patterns.

Validation and detection

  • Inventory MySQL Server versions across production, staging, and managed images.
  • Verify no supported deployment remains on MySQL Server 8.0.19 or earlier.
  • Confirm Ubuntu, Fedora, Gentoo, or vendor package advisories are applied where relevant.
  • Check firewall rules and security groups limiting MySQL network reachability.
  • Review MySQL logs for unexplained hangs, 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-2895 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-2895Attack 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.