LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2893: 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
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can let a highly privileged attacker crash or hang a vulnerable MySQL Server, causing a denial of service. It does not indicate data theft or data modification. Business urgency depends on whether affected MySQL 8.0.19 or earlier servers support critical services and whether privileged database access is tightly controlled.

Executive priority

Treat as a moderate availability risk. Prioritize remediation for mission-critical, internet-reachable, or shared-administration MySQL environments. This is less urgent than unauthenticated remote code execution, but database crashes can still create material service disruption.

Technical view

CVE-2020-2893 affects Oracle MySQL Server InnoDB in supported versions 8.0.19 and prior. The CVSS 3.0 score is 4.9 with network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most relevant for organizations running MySQL Server 8.0.19 or earlier, including packaged or embedded deployments referenced by Linux distribution and NetApp advisories. Risk is lower where privileged MySQL access is limited and network reachability is constrained.

Exploitation context

The provided sources describe the vulnerability as easily exploitable over multiple network protocols, but only by a high-privileged attacker. The source bundle does not show CISA KEV listing or cited evidence of active exploitation in the wild.

Researcher notes

The public description is concise and does not include root-cause details, proof-of-concept information, or exact fixed builds in the supplied bundle. Do not infer confidentiality or integrity impact; the stated impact is complete denial of service only.

Mitigation direction

  • Apply Oracle's April 2020 Critical Patch Update guidance for MySQL Server.
  • Use Ubuntu, Fedora, Gentoo, or NetApp advisories where those distributions or products apply.
  • Upgrade vulnerable MySQL Server deployments beyond 8.0.19 when vendor guidance supports it.
  • Restrict MySQL network access to trusted hosts and administrative paths.
  • Review and reduce high-privileged database accounts.

Validation and detection

  • Inventory MySQL Server versions and identify 8.0.19 or earlier deployments.
  • Confirm whether InnoDB is present in exposed MySQL Server instances.
  • Check package manager or vendor advisory status for applied security updates.
  • Review network paths that allow privileged users to reach MySQL.
  • Audit high-privileged MySQL accounts and recent administrative access.
Prepared
Confidence
high
Sources
9

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-2893 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-2893Attack 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.