CVE-2024-21157

What it actually does

The vulnerability in InnoDB allows a high-privileged network attacker to trigger a hang or repeatable crash, resulting in complete denial of service for the MySQL Server process.

Why it matters to the business

Successful exploitation leads to unplanned database outages that disrupt applications and services relying on MySQL, increasing operational recovery costs and potential revenue loss during downtime.

How an attack unfolds

An attacker with high-privileged network credentials connects to the MySQL Server via supported protocols and submits specially crafted requests that exploit a flaw in the InnoDB storage engine, forcing the server into a hung or crashed state.

How to fix it

Upgrade affected MySQL Server installations to the latest patched versions that address the InnoDB vulnerability; apply vendor security updates promptly and verify post-upgrade stability.

How to confirm the fix worked

Confirm the running MySQL version is no longer in the vulnerable range, review release notes for the fix, and perform controlled load testing to ensure InnoDB no longer exhibits crash behavior under similar conditions.

Typical attack path

1. Obtain high-privileged database credentials with network access
2. Establish a connection to the target MySQL Server using supported protocols
3. Transmit crafted queries or commands targeting the InnoDB component
4. Trigger repeated crashes or hangs to sustain denial of service

How to detect it

Examine MySQL error logs and system crash dumps for repeated InnoDB-related failures or abrupt server terminations; correlate with network connection logs from high-privileged accounts around the time of incidents.

What your security team should do

• Prioritize patching MySQL Server instances to the latest fixed versions within standard change windows
• Restrict high-privileged database accounts to only necessary network sources
• Enable and monitor MySQL error and crash logs for signs of repeated InnoDB failures
• Test failover and recovery procedures to minimize impact from potential DoS events