DoS via memory leak with WebSocket connections
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.1.0-M6, 10.0.12, 9.0.54, 8.5.72
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak. The object introduced to collect metrics for HTTP upgrade connections was not released for WebSocket connections once the connection was closed. This created a memory leak that, over time, could lead to a denial of service via an OutOfMemoryError.
Timeline
- CVE published
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Apache Software Foundation Apache Tomcat
Apache Tomcat 10 10.0.0-M10 to 10.0.11, Apache Tomcat 10 10.1.0-M1 to 10.1.0-M5, Apache Tomcat 9 9.0.40 to 9.0.53, Apache Tomcat 8 8.5.60 to 8.5.71
- org.apache.tomcat:tomcatMaven
From 10.1.0-M1 · fixed in 10.1.0-M6
- org.apache.tomcat:tomcatMaven
From 10.0.0-M1 · fixed in 10.0.12
- org.apache.tomcat:tomcatMaven
From 9.0.40 · fixed in 9.0.54
- org.apache.tomcat:tomcatMaven
From 8.5.60 · fixed in 8.5.72