CVE-2024-21060

What it actually does

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

Why it matters to the business

Database instances become unavailable, causing application downtime, interrupted services, and potential loss of revenue or productivity until the server is restarted.

How an attack unfolds

An attacker with high database privileges and network access connects to an affected MySQL instance and issues specially crafted requests targeting the Data Dictionary, causing the server process to hang or terminate.

How to fix it

Upgrade MySQL Server to a version newer than 8.0.36 and 8.3.0 as provided by Oracle. Restrict network access to the database and limit high-privileged accounts to trusted sources.

How to confirm the fix worked

Verify MySQL Server version is updated beyond the affected releases, review release notes for the fix, and confirm no anomalous crashes occur under expected high-privileged workloads.

Typical attack path

1. Obtain high-privileged database credentials with network access
2. Establish a connection to the MySQL Server via supported protocols
3. Send crafted Data Dictionary operations or queries
4. Trigger repeated server hang or crash to achieve denial of service

How to detect it

Review MySQL error logs and system event logs for repeated crashes or hangs coinciding with connections from high-privileged accounts; correlate with network access logs for unusual activity patterns.

What your security team should do

• Apply the latest MySQL Server patches immediately due to the age of the disclosure
• Enforce least-privilege access and network segmentation for database instances
• Monitor database availability metrics and alert on unexpected restarts or hangs
• Review and audit high-privileged account usage regularly