LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2174: 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.33 and prior and 8.0.23 and prior. Difficult to exploit 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.1 Base Score 4.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 4.4Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-2174 is a denial-of-service issue in Oracle MySQL Server's InnoDB component. An attacker already holding high privileges and network access could cause MySQL Server to hang or repeatedly crash. This is mainly an availability risk for databases still running affected MySQL 5.7 or 8.0 versions.

Executive priority

Treat this as a scheduled security update unless the database supports critical services or is reachable by many privileged users. The business risk is service disruption, not data theft based on the provided sources.

Technical view

Oracle reports affected MySQL Server versions are 5.7.33 and prior, and 8.0.23 and prior. The CVSS 3.1 score is 4.4 with network attack vector, high complexity, high privileges required, no user interaction, and high availability impact only.

Likely exposure

Exposure is most relevant where MySQL Server is network-accessible to privileged database users or service accounts. Internet exposure increases concern, but the source bundle does not say unauthenticated users can exploit it.

Exploitation context

The source bundle does not indicate known active exploitation, and CISA KEV status is false. Exploitation is described as difficult and requiring high privileges over network-accessible MySQL protocols.

Researcher notes

The available evidence identifies the affected component, version ranges, privilege requirement, and availability-only impact. It does not provide root-cause detail, exploit mechanics, or independent exploitation reports, so validation should stay version- and vendor-advisory based.

Mitigation direction

  • Inventory MySQL Server versions across production, staging, and managed appliances.
  • Prioritize systems running MySQL 5.7.33 or earlier, or 8.0.23 or earlier.
  • Apply Oracle, Fedora, NetApp, or other vendor-supported MySQL security updates.
  • Restrict MySQL network access to trusted application hosts and administrative networks.
  • Review privileged database accounts and remove unnecessary access.

Validation and detection

  • Confirm deployed MySQL Server versions are newer than the affected version ranges.
  • Verify patched packages came from Oracle, Fedora, NetApp, or the relevant platform vendor.
  • Check whether NetApp or appliance dependencies embed affected MySQL components.
  • Review database monitoring for unexplained hangs, crashes, or repeated restarts.
  • Confirm MySQL administrative access is limited to approved users and services.
Prepared
Confidence
high
Sources
7

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-2174 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.4 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/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 Server5.7.33 and prior, 8.0.23 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.