LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2412: 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.21 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-2412 is a MySQL Server optimizer flaw that can let a highly privileged remote attacker crash or hang the database. The main business risk is service outage, not data theft or modification. Affected MySQL Server versions are 8.0.21 and earlier.

Executive priority

Prioritize remediation for business-critical MySQL systems, especially those reachable across networks by administrative users. This is not the highest-severity class, but repeatable database crashes can still create material outage risk.

Technical view

Oracle describes the issue in MySQL Server, component Server: Optimizer. It is network reachable over multiple protocols, low complexity, no user interaction, but requires high privileges. Successful exploitation can cause a frequently repeatable crash or complete denial of service. CVSS 3.1 is 4.9.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.21 or earlier remains deployed and high-privileged database accounts can connect over the network. Internet exposure increases operational risk, but the privilege requirement limits likelihood.

Exploitation context

The provided bundle does not show CISA KEV listing or any cited evidence of active exploitation. Treat this as a denial-of-service risk requiring privileged access, not as confirmed exploitation in the wild.

Researcher notes

Evidence supports availability impact only: no confidentiality or integrity impact is listed. The high-privilege requirement is central to triage. Public details in the bundle do not identify exploit mechanics, proof-of-concept availability, or product-specific downstream fixes beyond referenced advisories.

Mitigation direction

  • Apply Oracle guidance from the July 2021 Critical Patch Update.
  • Upgrade MySQL Server beyond affected 8.0.21 and prior versions where applicable.
  • Restrict network access to MySQL Server to trusted hosts only.
  • Review and reduce high-privileged database accounts with network access.
  • Check downstream vendor guidance, including NetApp, if using bundled MySQL components.

Validation and detection

  • Inventory all MySQL Server instances and record exact versions.
  • Confirm no production instance remains on 8.0.21 or earlier.
  • Review firewall, security group, and database listener exposure.
  • Audit high-privileged MySQL accounts allowed remote login.
  • Validate patch status against Oracle’s July 2021 CPU guidance.
Prepared
Confidence
high
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-2412 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-2412Attack 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.21 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.