LiveActive security incident?Get immediate response
CVE Record

CVE-2020-2903: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Connection Handling).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Connection Handling). 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-2903 can let a high-privileged network attacker crash or hang MySQL Server. It does not indicate data theft or data modification, but it can disrupt applications that depend on MySQL availability.

Executive priority

Treat as a service-availability risk for business systems backed by MySQL. Prioritize internet-exposed or broadly reachable databases, but urgency is moderated because exploitation requires high privileges.

Technical view

The issue affects Oracle MySQL Server 8.0.19 and prior in Server: Connection Handling. The CVSS vector is network reachable, low complexity, high privileges required, no user interaction, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.19 or earlier is reachable over a network by users or services with high database privileges.

Exploitation context

The source bundle does not show CISA KEV listing or confirm active exploitation. Oracle describes it as easily exploitable by a high-privileged attacker with network access via multiple protocols, resulting in denial of service.

Researcher notes

No CWE is provided in the bundle. Public details are limited to component, affected versions, CVSS, and denial-of-service impact, so validation should focus on version exposure, privilege paths, and vendor advisory alignment.

Mitigation direction

  • Inventory MySQL Server instances and identify versions 8.0.19 or earlier.
  • Apply Oracle or operating-system vendor updates referenced by the relevant advisory.
  • Restrict MySQL network exposure to trusted hosts and application networks.
  • Review and reduce high-privileged database accounts where operationally possible.
  • Monitor MySQL availability and crash patterns until remediation is complete.

Validation and detection

  • Confirm each MySQL instance reports a version newer than the affected range.
  • Check package manager or vendor advisory status for Oracle, Ubuntu, Fedora, or Gentoo builds.
  • Verify firewall and security group rules limit MySQL access paths.
  • Review database accounts with elevated privileges and remove unnecessary access.
  • Correlate MySQL error logs with unexplained hangs or repeatable crashes.
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-2903 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-2903Attack 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.