CVE-2024-21218

What it actually does

Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server.

Why it matters to the business

Disrupts database availability leading to operational downtime; high privileged network access required limits blast radius but affects organizations relying on MySQL with 347 downstream dependents.

How an attack unfolds

A high privileged attacker with network access connects via supported protocols and triggers the InnoDB flaw to induce repeated crashes or hangs without needing additional user interaction.

How to fix it

Upgrade affected MySQL Server versions (8.0.39 and prior, 8.4.2 and prior, 9.0.1 and prior) to fixed releases; apply vendor patches promptly given the published date and ecosystem prevalence.

How to confirm the fix worked

Verify MySQL Server version is newer than listed affected releases and test that the InnoDB component no longer allows high-privileged network users to induce crashes.

Typical attack path

1. Obtain high privileged network credentials for MySQL Server
2. Establish connection using multiple protocols
3. Send crafted requests targeting InnoDB component
4. Trigger hang or repeatable crash resulting in denial of service

How to detect it

Review database server logs for repeated crash or hang events initiated by high privileged network sessions; correlate with authentication and protocol access records.

What your security team should do

• Prioritize patching MySQL instances with high privileged network exposure
• Review and restrict unnecessary high privileged accounts with network access
• Monitor for availability anomalies in database services