Vulnerability Details : CVE-2018-8037

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.
Published 2018-08-02 14:29:00
Updated 2023-12-08 16:41:19
Source Apache Software Foundation
View at NVD,   CVE.org

Products affected by CVE-2018-8037

Threat overview for CVE-2018-8037

Top countries where our scanners detected CVE-2018-8037
Top open port discovered on systems with this issue 80
IPs affected by CVE-2018-8037 63,953
Threat actors abusing to this issue? Yes
Find out if you* are affected by CVE-2018-8037!
*Directly or indirectly through your vendors, service providers and 3rd parties. Powered by attack surface intelligence from SecurityScorecard.

Exploit prediction scoring system (EPSS) score for CVE-2018-8037

EPSS FAQ
0.40%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 73 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2018-8037

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
4.3
 MEDIUM AV:N/AC:M/Au:N/C:P/I:N/A:N
8.6
2.9
 NIST
5.9
 MEDIUM CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
2.2
3.6
 NIST

CWE ids for CVE-2018-8037

References for CVE-2018-8037

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!
Accept Close