CVE-2018-8037

published 2 Aug 2018 · updated 16 Sep 2024

If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition…

5.5MediumEPSS 11%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 11%. No fixed version is recorded.

If an async request was completed by the application at the same time as the container triggered the async timeout, a race condition existed that could result in a user seeing a response intended for a different user. An additional issue was present in the NIO and NIO2 connectors that did not correctly track the closure of the connection when an async request was completed by the application and timed out by the container at the same time. This could also result in a user seeing a response intended for another user. Versions Affected: Apache Tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Apache Software Foundation=8.5.5 to 8.5.31, =9.0.0.M9 to 9.0.9

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2018-8037 severity on Zeptric[![CVE-2018-8037](https://zeptric.io/badge/cve/CVE-2018-8037.svg)](https://zeptric.io/cve/CVE-2018-8037)