LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2390: 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.34 and prior and 8.0.25 and prior. Difficult to exploit vulnerability allows unauthenticated 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 5.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 5.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 flaw in Oracle MySQL Server's InnoDB component. A remote unauthenticated attacker could cause the database to hang or crash repeatedly, but the published CVSS notes high attack complexity and no confidentiality or integrity impact. The main business risk is outage for applications relying on affected MySQL versions.

Executive priority

Treat this as a service-resilience issue, not a data-theft issue based on the provided CVSS. Prioritize exposed or business-critical MySQL systems, especially those supporting revenue, authentication, or operational workflows.

Technical view

CVE-2021-2390 affects Oracle MySQL Server 5.7.34 and prior and 8.0.25 and prior, component InnoDB. CVSS 3.1 is 5.9: network exploitable, high complexity, no privileges or user interaction, unchanged scope, availability high, confidentiality and integrity none.

Likely exposure

Exposure is most likely where affected MySQL Server versions are reachable over a network by untrusted users or adjacent application tiers. Internet-facing database listeners, shared hosting, and vendor products embedding MySQL deserve priority review.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The vulnerability is described as difficult to exploit, but successful exploitation could cause complete denial of service through hangs or repeatable crashes.

Researcher notes

No CWE is supplied in the bundle. Public details identify InnoDB and denial of service only; avoid assuming data access or code execution. Validate exposure through version, reachability, and vendor dependency mapping rather than exploit reproduction.

Mitigation direction

  • Review Oracle July 2021 CPU guidance for the applicable MySQL release line.
  • Upgrade affected MySQL Server versions to a vendor-supported fixed release.
  • Check NetApp guidance if using NetApp products that include or depend on MySQL.
  • Restrict MySQL network exposure to trusted application hosts and administration paths.
  • Maintain backups and service recovery procedures for database outage scenarios.

Validation and detection

  • Inventory MySQL Server versions across production, staging, and managed appliances.
  • Flag MySQL 5.7.34 and prior, and 8.0.25 and prior, as affected.
  • Confirm database listener exposure and whether untrusted network paths can reach it.
  • Review vendor advisories for embedded MySQL dependencies and patched product versions.
  • Check monitoring history for unexplained MySQL hangs or repeatable crashes.
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-2021-2390 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
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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
4Source 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
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2021-2390Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/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.34 and prior, 8.0.25 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.