Response mix-up with WebSocket concurrent send and close
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.
CVE-2022-25762
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2022-25762
Apache Tomcat
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "Apache Software Foundation",
"product": "Apache Tomcat",
"versions": [
{
"status": "affected",
"version": "Apache Tomcat 9 9.0.0.M1 to 9.0.20"
},
{
"status": "affected",
"version": "Apache Tomcat 8.5 8.5.0 to 8.5.75"
}
]
}
]- Related CVEs
- CVE-2022-25762
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #16071 · Revision 1
- Added to Heist Feed
- Publisher date