CVE-2024-21135

What it actually does

The flaw in the MySQL Server Optimizer component permits a high-privileged network attacker to trigger repeated server hangs or crashes, resulting in complete denial of service.

Why it matters to the business

Database services can be taken offline on demand by insiders or compromised high-privilege accounts, interrupting applications and business processes that rely on MySQL availability.

How an attack unfolds

An attacker who already possesses high-privilege network credentials connects to the MySQL server using any supported protocol and issues specially crafted statements that exercise the Optimizer, causing the server process to hang or terminate.

How to fix it

Upgrade affected MySQL Server installations (8.0.36 and earlier, 8.3.0 and earlier) to the latest vendor-supplied patched release. Restrict high-privilege accounts to trusted networks and review unnecessary network-exposed accounts.

How to confirm the fix worked

Verify the running MySQL version is no longer in the affected range, review release notes for the Optimizer fix, and confirm the server remains stable under normal privileged query workloads.

Typical attack path

1. Obtain high-privilege database credentials with network access
2. Connect to the MySQL instance over any supported protocol
3. Submit crafted queries that reach the vulnerable Optimizer code path
4. Observe server hang or crash and repeat to maintain denial of service

How to detect it

Monitor MySQL error logs and process crash dumps for repeated optimizer-related failures, correlate with successful high-privilege logins from unexpected sources, and watch for abrupt service restarts without administrative action.

What your security team should do

• Apply the latest MySQL patches immediately on all instances
• Audit and minimize the number of high-privilege accounts with network access
• Enable connection and query logging to detect anomalous privileged activity
• Test failover and recovery procedures for database outages