LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2194: 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. 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.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/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 an availability issue in Oracle MySQL Server InnoDB. An attacker who already has high MySQL privileges and network access can crash or hang the database. It does not indicate data theft or modification, but can interrupt services that depend on affected MySQL versions.

Executive priority

Treat as a planned remediation item unless the affected database supports critical services or has broad privileged access. The business risk is service outage, not known data compromise, based on the supplied sources.

Technical view

CVE-2021-2194 affects MySQL Server 5.7.33 and prior and 8.0.23 and prior in InnoDB. CVSS 3.1 is 4.9: network attack vector, low complexity, high privileges required, no user interaction, and high availability impact only.

Likely exposure

Exposure is most likely where affected MySQL Server instances accept network connections from high-privileged users or service accounts. Internet exposure increases operational risk, but the vulnerability still requires high privileges.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The main credible concern is misuse by a privileged database user, compromised admin account, or overly powerful application account to cause repeatable denial of service.

Researcher notes

The record provides no CWE, root-cause detail, exploit procedure, or fixed-version mapping beyond Oracle CPU references. Analysis should stay focused on affected MySQL versions, privilege requirements, network reachability, and availability impact.

Mitigation direction

  • Apply Oracle April 2021 CPU guidance or newer vendor-provided MySQL updates.
  • Update Fedora-provided MySQL or related packages where applicable.
  • Review NetApp advisory if MySQL is embedded in NetApp-managed environments.
  • Restrict network access to MySQL administrative interfaces and trusted hosts.
  • Reduce unnecessary high-privilege MySQL accounts and service account permissions.

Validation and detection

  • Inventory MySQL Server versions and flag 5.7.33 and prior or 8.0.23 and prior.
  • Confirm whether affected instances use InnoDB and accept network connections.
  • Review privileged MySQL accounts and where they can authenticate from.
  • Check database monitoring for unexplained hangs, crashes, or repeated restarts.
  • Verify vendor updates are applied in staging before production rollout.
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-2194 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.1)
Known Exploited
No
Published

Vector: CVSS:3.1/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
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.9CVSS 3.1MediumCVSS:3.1/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.1 score

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

Vector: CVSS:3.1/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 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.