Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2024-23672

MEDIUM

CVE-2024-23672 is a medium-severity (CVSS 6.3) CWE-459 vulnerability in org.apache.tomcat:tomcat-websocket. O3 Security confirms whether CVE-2024-23672 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Tomcat: WebSocket DoS with incomplete closing handshake

Also known asBIT-tomcat-2024-23672GHSA-v682-8vv8-vpwr
Published
Mar 13, 2024
Updated
Jul 15, 2026
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed

Blast Radius

8 pkgs affected
org.apache.tomcat:tomcat-websocketorg.apache.tomcat:tomcat-websocketorg.apache.tomcat:tomcat-websocketorg.apache.tomcat:tomcat-websocketorg.apache.tomcat.embed:tomcat-embed-websocketorg.apache.tomcat.embed:tomcat-embed-websocketorg.apache.tomcat.embed:tomcat-embed-websocketorg.apache.tomcat.embed:tomcat-embed-websocket

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Denial of Service via incomplete cleanup vulnerability in Apache Tomcat. It was possible for WebSocket clients to keep WebSocket connections open leading to increased resource consumption.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98.

Older, EOL versions may also be affected.

Users are recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat-websocket11.0.0-M1&&< 11.0.0-M1711.0.0-M17
Mavenorg.apache.tomcat:tomcat-websocket10.1.0-M1&&< 10.1.1910.1.19
Mavenorg.apache.tomcat:tomcat-websocket9.0.0-M1&&< 9.0.869.0.86
Mavenorg.apache.tomcat:tomcat-websocket8.5.0&&< 8.5.998.5.99
Mavenorg.apache.tomcat.embed:tomcat-embed-websocket11.0.0-M1&&< 11.0.0-M1711.0.0-M17
Mavenorg.apache.tomcat.embed:tomcat-embed-websocket10.1.0-M1&&< 10.1.1910.1.19

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-websocket. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.tomcat:tomcat-websocket to 11.0.0-M17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-23672 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-23672 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-23672. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Denial of Service via incomplete cleanup vulnerability in Apache Tomcat. It was possible for WebSocket clients to keep WebSocket connections open leading to increased resource consumption.This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M16, from 10.1.0-M1 through 10.1.18, from 9.0.0-M1 through 9.0.85, from 8.5.0 through 8.5.98. Older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0-M17, 10.1.19, 9.0.86 or 8.5.99 which fix the issue.
O3 Security · Impact-Aware SCA

Is CVE-2024-23672 in your dependencies?

O3 detects CVE-2024-23672 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.