CVE-2024-21200

What it actually does

The vulnerability in the Optimizer component allows a high-privileged network attacker to trigger a denial of service by causing the MySQL Server to hang or crash repeatedly.

Why it matters to the business

Successful exploitation leads to database unavailability, disrupting dependent applications and services until the server is restarted; low EPSS and no KEV status indicate limited immediate widespread risk but still requires attention for high-availability environments.

How an attack unfolds

An attacker with high database privileges connects over the network and submits specially crafted queries that exploit a flaw in the query optimizer, resulting in a server hang or crash.

How to fix it

Upgrade affected MySQL Server installations beyond version 8.0.35; for the listed package update to version 5.4.0 or later as specified in fixed versions.

How to confirm the fix worked

Confirm MySQL version is updated past 8.0.35 and perform stability testing with optimizer-intensive workloads to ensure no hangs or crashes occur.

Typical attack path

1. Obtain high-privileged database credentials
2. Establish network connection to MySQL server using supported protocols
3. Execute malicious queries targeting the optimizer
4. Induce repeated crashes or hangs to achieve denial of service

How to detect it

Review MySQL error logs and system event logs for repeated server crashes or hangs around optimizer-related operations; correlate with network connections from privileged accounts.

What your security team should do

• Apply available patches or upgrades immediately to eliminate the denial-of-service vector
• Audit and minimize high-privileged network access accounts
• Monitor database logs for crash patterns post-remediation
• Review EPSS trend stability before deprioritizing