CVE-2022-25762
Published: 13 May 2022
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.
Priority
Status
Package | Release | Status |
---|---|---|
tomcat8 Launchpad, Ubuntu, Debian |
bionic |
Needs triage
|
upstream |
Needs triage
|
|
tomcat9 Launchpad, Ubuntu, Debian |
kinetic |
Not vulnerable
|
bionic |
Needs triage
|
|
focal |
Not vulnerable
(9.0.31-1ubuntu0.2)
|
|
impish |
Not vulnerable
|
|
jammy |
Not vulnerable
|
|
lunar |
Not vulnerable
|
|
upstream |
Released
(9.0.22-1)
|
|
mantic |
Not vulnerable
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 8.6 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | Low |
Availability impact | Low |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L |
References
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25762
- https://github.com/apache/tomcat/commit/e2d5a040b962a904db5264b3cb3282c6b05f823c (9.0.21)
- https://github.com/apache/tomcat/commit/7046644bf361b89afc246b6643e24ce2ae60cacc (9.0.21)
- https://github.com/apache/tomcat/commit/339b40bc07bdba9ded565929b9a3448c5a78f015 (9.0.21)
- https://github.com/apache/tomcat/commit/65fb1ee548111021edde247f3b3c409ec95a5183 (9.0.21)
- https://github.com/apache/tomcat/commit/01f2cf25b270a84d0daeefc4f215aa2f56e1df99 (8.5.76)
- https://lists.apache.org/thread/6ckmjfb1k61dyzkto9vm2k5jvt4o7w7c
- NVD
- Launchpad
- Debian