Apache Tomcat Race Condition vulnerability
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-8037US | medium5.9 | — | ||
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 re… | ||||
references
External citations — patches, advisories, analysis.
- http://mail-archives.us.apache.org/mod_mbox/www-announce/201807.mbox/%3C20180722090623.GA92700%40minotaur.apache.org%3EWEB
- http://mail-archives.us.apache.org/mod_mbox/www-announce/201808.mbox/%3C0c616b4d-4e81-e7f8-b81d-1bb4c575aa33%40apache.org%3EWEB
- http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.htmlWEB
- https://access.redhat.com/errata/RHSA-2018:2867WEB
- https://access.redhat.com/errata/RHSA-2018:2868WEB
- https://access.redhat.com/errata/RHSA-2019:1529WEB
- https://github.com/apache/tomcatPACKAGE
- https://github.com/apache/tomcat/commit/4c04369c287233ea2e8e5135f6c31d02e2d76293WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan