CVE-2024-21236

What it actually does

The flaw in the InnoDB component allows a high privileged network attacker to trigger a hang or repeatable crash resulting in complete denial of service to the MySQL Server.

Why it matters to the business

Database downtime can interrupt dependent applications and services across the ecosystem; slight EPSS increase and 729 days since publication add modest urgency for patching despite low overall exploit likelihood.

How an attack unfolds

An authenticated high-privileged attacker with network access sends specially crafted requests over supported protocols to the InnoDB component, causing the server process to hang or crash.

How to fix it

Upgrade affected MySQL Server installations to versions later than 8.0.39, 8.4.2, and 9.0.1; for the listed Maven artifact apply org.jvnet.hudson.plugins:favorite 2.3.0 or newer.

How to confirm the fix worked

Verify MySQL Server version strings post-upgrade and confirm the InnoDB component no longer accepts the previously crashing request patterns; test connectivity and stability under load.

Typical attack path

1. Obtain high-privileged network credentials for the MySQL instance
2. Establish a connection using any supported protocol
3. Transmit malicious packets crafted to trigger the InnoDB flaw
4. Observe server hang or crash achieving denial of service

How to detect it

Review database error logs and process crash dumps for repeated InnoDB assertion failures or abrupt terminations around the time of suspected activity; correlate with privileged login events.

What your security team should do

• Prioritize patching internet-facing or high-value MySQL instances within standard change windows
• Review privileged account access and network ACLs to reduce attack surface
• Monitor EPSS trend for any further rise indicating increased exploitation interest