CVE-2024-21051

What it actually does

High-privileged network attacker can trigger a hang or repeatable crash in the MySQL Server DML component, resulting in complete denial of service.

Why it matters to the business

Database services become unavailable, interrupting applications and business operations that depend on MySQL until the server is restarted.

How an attack unfolds

An attacker with high-privileged network credentials connects to the MySQL Server over supported protocols and issues crafted DML statements that cause the server process to hang or crash.

How to fix it

Upgrade MySQL Server to a version later than 8.0.34 that contains the fix for this issue and apply Oracle's latest security patches promptly.

How to confirm the fix worked

Verify the installed MySQL version is newer than 8.0.34, review release notes for the DML component fix, and monitor server stability under load after patching.

Typical attack path

1. Obtain or compromise high-privileged MySQL account with network access
2. Connect to the MySQL Server using multiple protocols
3. Submit specially crafted DML statements
4. Observe server hang or crash leading to denial of service

How to detect it

Review MySQL error logs and system logs for repeated crashes or hangs immediately following DML activity from privileged accounts; correlate with authentication events from network sources.

What your security team should do

• Apply the MySQL Server update that resolves this vulnerability as soon as possible
• Restrict network access to the MySQL service to only trusted clients and networks
• Enforce least-privilege database accounts to limit the pool of high-privileged users
• Enable monitoring for unexpected MySQL process crashes and availability alerts