TomcatWeb server / proxy · Apache
CVE-2024-23672
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDenial 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIncomplete cleanup in Apache Tomcat's WebSocket implementation allows WebSocket clients to keep connections open indefinitely, leading to increased resource consumption (memory, file descriptors) and potential denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TomcatWeb server / proxy
>= 8.5.0, < 8.5.99>= 9.0.0, < 9.0.86>= 10.1.0, < 10.1.19= 11.0.0
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 39= 40CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Tomcat installation locationCheck for Tomcat installation directories (common paths: /etc/tomcat*, /usr/share/tomcat*, /opt/tomcat*, or check for CATALINA_HOME environment variable)Affected if Tomcat is installed on the system
-
Determine Tomcat versionLook for VERSION file in the Tomcat conf directory, or check the jar file name in lib/ (e.g., catalina.jar metadata) using: jar -xf catalina.jar org/apache/catalina/util/ServerInfo.properties && cat org/apache/catalina/util/ServerInfo.propertiesAffected if Version falls within 8.5.0-8.5.98, 9.0.0-9.0.85, 10.1.0-10.1.18, or exactly 11.0.0
-
Check if WebSocket is deployedSearch for WebSocket endpoint classes (classes implementing javax.websocket.Endpoint or jakarta.websocket.Endpoint) in deployed web applications under webapps/ directory, or check for websocket-related JAR files in lib/ (like websocket-api.jar)Affected if WebSocket endpoints are deployed or WebSocket libraries are present
-
Inspect WebSocket connection timeout configurationReview server.xml for Connector configurations with connectionTimeout settings and check for any jakarta.websocket.* or javax.websocket.* session timeout configurations in deployed applicationsAffected if No WebSocket session timeout is configured, allowing connections to persist indefinitely
You are affected if you run a vulnerable Tomcat version (8.5.0-8.5.98, 9.0.0-9.0.85, 10.1.0-10.1.18, or 11.0.0) and have WebSocket endpoints deployed without connection timeout limits.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.5.999.0.8610.1.19
Upgrade to fixed versions (11.0.0-M17, 10.1.19, 9.0.86, or 8.5.99) or implement WebSocket connection timeouts to limit resource consumption from lingering connections.
Upgrade to Apache Tomcat 8.5.99, 9.0.86, 10.1.19, or 11.0.0-M17 depending on your current major version line
- 1. Identify the currently installed Apache Tomcat version using the version.sh script or by checking the CATALINA_HOME/lib/catalina.jar manifest.
- 2. Stop all Tomcat instances that are currently running.
- 3. Download the appropriate fixed Tomcat version for your major version line: 8.5.99, 9.0.86, 10.1.19, or 11.0.0-M17 from the official Apache Tomcat download page (tomcat.apache.org).
- 4. Create a backup of your existing Tomcat installation directory, including all configuration files, web applications, and any custom libraries.
- 5. Extract the new Tomcat version to a temporary location.
- 6. Copy your existing configuration files (server.xml, context.xml, web.xml, etc.) from the backup to the new installation, reviewing for any deprecated settings.
- 7. Restore any custom libraries or web applications from the backup to the new installation as needed.
- 8. Start the Tomcat instance and verify the WebSocket functionality is working correctly.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Tomcat
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23672 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23672 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data