CVE-2024-20962

What it actually does

A flaw in the MySQL Server Optimizer allows a low-privileged network attacker to trigger a denial of service by causing the server to hang or crash repeatedly.

Why it matters to the business

Attackers can disrupt database availability, leading to downtime for applications relying on MySQL and interrupting business operations without data theft or corruption.

How an attack unfolds

An authenticated attacker with low privileges connects to the MySQL server via supported network protocols and submits crafted queries that exploit weaknesses in the optimizer component, resulting in repeated hangs or crashes.

How to fix it

Upgrade MySQL Server to a version that resolves the optimizer vulnerability in the affected 8.0 and 8.2 release lines.

How to confirm the fix worked

Confirm the installed MySQL version is newer than the affected releases, review release notes for the specific fix, and perform stability testing under load with typical query patterns.

Typical attack path

1. Obtain low-privileged database credentials
2. Establish a network connection to the MySQL server
3. Issue specially crafted queries targeting the optimizer
4. Induce server hang or crash to achieve denial of service

How to detect it

Inspect MySQL error and slow-query logs for repeated optimizer crashes or hangs, correlate with authentication events from low-privileged accounts, and review system logs for unexpected server restarts.

What your security team should do

• Apply available MySQL updates as soon as possible to restore availability protections
• Enforce least-privilege database accounts and network segmentation
• Enable query logging and monitor for anomalous optimizer-related errors
• Test failover and restart procedures to reduce downtime impact