SECUFOCUSNOW
Home›CVE index›CVE-2022-25762
ReviewHigh

CVE-2022-25762

Apache Software Foundation Apache Tomcat, tomcat, agile product lifecycle management

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.

CVSS
8.6
EPSS
8.40%
94.6% percentile
CISA KEV
Not listed
Published
2022.05.13
PRIORITY ASSESSMENT

Review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability8.40%
Technical severityCVSS 8.6

Vulnerability overview

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.

Affected product and versions

Product
Apache Software Foundation Apache Tomcat, tomcat, agile product lifecycle management
Affected versions
>= Apache Tomcat 9 9.0.0.M1 to 9.0.20, >= Apache Tomcat 8.5 8.5.0 to 8.5.75, >= 8.5.0 < 8.5.76, >= 9.0.0 < 9.0.21, 9.3.6
Fixed versions
8.5.76, 9.0.21

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Apache Software Foundation Apache Tomcat, tomcat, agile product lifecycle management and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
CWE
CWE-404