LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2201: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Partition).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Partition). Supported versions that are affected are 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
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-2201 can let a highly privileged user crash or hang a vulnerable MySQL Server remotely. The business impact is service outage, not data theft or tampering. Exposure is most relevant where MySQL 8.0.23 or earlier is still running and reachable over MySQL-supported network protocols.

Executive priority

Treat this as a reliability risk for business-critical databases. It is not described as a data breach issue, but a privileged attacker could take MySQL offline. Prioritize patching internet-adjacent, shared, or critical MySQL systems first.

Technical view

Oracle describes a MySQL Server vulnerability in the Server: Partition component affecting supported versions 8.0.23 and prior. The CVSS 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H, indicating easy network exploitation by a high-privileged attacker with availability-only impact: complete denial of service through hang or repeatable crash.

Likely exposure

Organizations are exposed if they run Oracle MySQL Server 8.0.23 or earlier, especially where highly privileged database accounts can connect over a network. Systems with tight administrative access controls have reduced practical risk, but outage impact may still be material for critical databases.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The vulnerability requires high privileges, so likely misuse scenarios include compromised database administrator accounts, overly broad service accounts, or malicious insiders with elevated MySQL access.

Researcher notes

The available evidence identifies the affected component and impact but does not provide root-cause detail, exploit prerequisites beyond high privileges, or a named fixed version. Avoid assuming exploit availability. Validation should focus on version, privilege model, network reachability, and vendor CPU status.

Mitigation direction

  • Review Oracle CPU April 2021 guidance for the applicable MySQL Server update path.
  • Upgrade affected MySQL Server 8.0.23 or earlier deployments per vendor guidance.
  • Restrict network access to MySQL to trusted hosts and administrative paths.
  • Audit and reduce high-privilege MySQL accounts where operationally possible.
  • Monitor MySQL availability and crash patterns until remediation is complete.

Validation and detection

  • Inventory MySQL Server versions and identify any 8.0.23 or earlier instances.
  • Confirm whether vulnerable instances are reachable over network protocols.
  • Review privileged MySQL accounts and service account permissions.
  • Check whether Oracle April 2021 CPU or later vendor fixes are applied.
  • Review database logs for unexplained hangs, crashes, or repeatable restarts.
Prepared
Confidence
medium
Sources
4

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-2201 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
3Source 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-2201Attack 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 Server8.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.