Response mix-up with WebSocket concurrent send and close
- 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 8.5.76, 9.0.21, 8.5.75, 9.0.20
- 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
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Apache Software Foundation Apache Tomcat
Apache Tomcat 9 9.0.0.M1 to 9.0.20, Apache Tomcat 8.5 8.5.0 to 8.5.75
- tomcatBitnami
From 8.5.0 · fixed in 8.5.76; From 9.0.0 · fixed in 9.0.21
- org.apache.tomcat:tomcatMaven
From 8.5.0 · fixed in 8.5.75
- org.apache.tomcat:tomcatMaven
From 9.0.0M1 · fixed in 9.0.20