Back

CRITICAL

tomcat: Due to a mishandling of close in NIO/NIO2 connectors user sessions can get mixed up

Published Aug 2, 2018

Description

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 products

Remediation

No remediation recorded yet.

Metrics

Weaknesses (1)

References (51)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner apache
Published Aug 2, 2018
Updated Sep 16, 2024
Reserved Mar 9, 2018
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Important
Public date Jul 22, 2018
GHSA-6V52-MJ5R-7J2M