LiveActive security incident?Get immediate response
CVE Record

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

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

This is a denial-of-service risk in Oracle MySQL Server. A highly privileged attacker who can reach the database over the network could make affected MySQL servers hang or crash repeatedly, disrupting applications that depend on them.

Executive priority

Treat as a timely maintenance and resilience issue, not an emergency internet-wide takeover risk. Prioritize systems supporting critical applications, shared database platforms, and environments with many privileged database users.

Technical view

CVE-2020-2923 affects MySQL Server 8.0.19 and prior in the Server: Optimizer component. The CVSS 3.0 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.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.19 or earlier is still running and reachable by privileged database users over supported network protocols. Internet exposure is not required, but network access to the MySQL service is.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The issue is described as easily exploitable, but it requires high privileges, limiting attacker population to compromised or malicious privileged database users.

Researcher notes

No CWE is provided in the bundle. Analysis should focus on availability impact in the optimizer component, privilege boundaries around high-privileged MySQL users, and whether downstream vendor packages incorporated Oracle’s April 2020 fixes.

Mitigation direction

  • Patch or upgrade MySQL Server using Oracle April 2020 CPU guidance.
  • Apply applicable Ubuntu, Fedora, Gentoo, NetApp, or other vendor packages.
  • Limit network access to MySQL services to trusted hosts only.
  • Review and reduce high-privileged MySQL accounts where possible.
  • Monitor database availability and crash patterns until remediation is complete.

Validation and detection

  • Inventory MySQL Server instances and identify versions 8.0.19 or earlier.
  • Confirm vendor security updates covering CVE-2020-2923 are installed.
  • Verify MySQL network exposure is restricted to expected systems.
  • Review privileged database accounts for unnecessary access.
  • Check database logs and service monitors for repeated crashes or hangs.
Prepared
Confidence
high
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-2923 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-2923Attack 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.