Response mix-up with WebSocket concurrent send and close
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache Tomcat | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| pki-core:10.6-8030020200911215836.5ff1562f | cpe:/a:redhat:enterprise_linux:8 | RHSA-2020:4847 | 2020-11-04T00:00:00Z |
| pki-deps:10.6-8030020200527165326.30b713e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2020:4847 | 2020-11-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-4051 | 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. |
Github GHSA |
GHSA-h3ch-5pp2-vh6w | Improper socket reuse in Apache Tomcat |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 8.4% (8.405% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oracle agile Product Lifecycle Management
|
|
| CPEs | cpe:2.3:a:oracle:agile_product_lifecycle_management:9.3.6:*:*:*:*:*:*:* | |
| Vendors & Products |
Oracle agile Plm
|
Oracle agile Product Lifecycle Management
|