CVE-2024-20982

What it actually does

High-privileged network attacker can trigger a flaw in the MySQL Server Optimizer to cause a hang or repeatable crash, resulting in complete denial of service.

Why it matters to the business

Database services become unavailable, causing application downtime and operational disruption until the server is restarted.

How an attack unfolds

An authenticated high-privileged user connects over supported network protocols and submits specially crafted statements that exercise the optimizer bug, forcing the server process to hang or terminate.

How to fix it

Upgrade MySQL Server 8.0.x to the latest patch level beyond 8.0.35 and 8.2.x beyond 8.2.0; apply vendor security updates as they become available and verify the fix in release notes.

How to confirm the fix worked

Confirm server version is updated; review release notes for the specific optimizer fix; perform controlled testing with privileged accounts to ensure no crash occurs on previously triggering statements.

Typical attack path

1. Obtain high-privileged database credentials
2. Establish network connection to MySQL using supported protocols
3. Issue crafted queries or administrative commands that reach the Optimizer component
4. Trigger the flaw to induce hang or crash

How to detect it

Inspect MySQL error logs for repeated crash or hang entries tied to the optimizer; correlate with audit logs showing high-privileged connections followed by complex queries; watch for sudden service restarts without administrative action.

What your security team should do

• Prioritize patching internet-facing or critical MySQL instances within standard change windows
• Restrict high-privileged accounts to trusted networks and require strong authentication
• Enable query logging and monitor for unusual optimizer-related statements from privileged users
• Test database failover and recovery procedures to minimize downtime impact