First published: Sun Jul 22 2018(Updated: )
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.
Credit: security@apache.org security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jws5-tomcat | <0:9.0.7-12.redhat_12.1.el6 | 0:9.0.7-12.redhat_12.1.el6 |
redhat/jws5-tomcat | <0:9.0.7-12.redhat_12.1.el7 | 0:9.0.7-12.redhat_12.1.el7 |
debian/tomcat9 | 9.0.31-1~deb10u6 9.0.31-1~deb10u10 9.0.43-2~deb11u6 9.0.43-2~deb11u9 9.0.70-2 | |
Apache Tomcat | >=8.5.5<=8.5.31 | |
Apache Tomcat | >=9.0.1<=9.0.9 | |
Apache Tomcat | =9.0.0 | |
Apache Tomcat | =9.0.0-m10 | |
Apache Tomcat | =9.0.0-m11 | |
Apache Tomcat | =9.0.0-m12 | |
Apache Tomcat | =9.0.0-m13 | |
Apache Tomcat | =9.0.0-m14 | |
Apache Tomcat | =9.0.0-m15 | |
Apache Tomcat | =9.0.0-m16 | |
Apache Tomcat | =9.0.0-m17 | |
Apache Tomcat | =9.0.0-m18 | |
Apache Tomcat | =9.0.0-m19 | |
Apache Tomcat | =9.0.0-m20 | |
Apache Tomcat | =9.0.0-m21 | |
Apache Tomcat | =9.0.0-m22 | |
Apache Tomcat | =9.0.0-m23 | |
Apache Tomcat | =9.0.0-m24 | |
Apache Tomcat | =9.0.0-m25 | |
Apache Tomcat | =9.0.0-m26 | |
Apache Tomcat | =9.0.0-m27 | |
Apache Tomcat | =9.0.0-m9 | |
Debian Debian Linux | =9.0 | |
Apache Tomcat | =9.0.0-milestone10 | |
Apache Tomcat | =9.0.0-milestone11 | |
Apache Tomcat | =9.0.0-milestone12 | |
Apache Tomcat | =9.0.0-milestone13 | |
Apache Tomcat | =9.0.0-milestone14 | |
Apache Tomcat | =9.0.0-milestone15 | |
Apache Tomcat | =9.0.0-milestone16 | |
Apache Tomcat | =9.0.0-milestone17 | |
Apache Tomcat | =9.0.0-milestone18 | |
Apache Tomcat | =9.0.0-milestone19 | |
Apache Tomcat | =9.0.0-milestone20 | |
Apache Tomcat | =9.0.0-milestone21 | |
Apache Tomcat | =9.0.0-milestone22 | |
Apache Tomcat | =9.0.0-milestone23 | |
Apache Tomcat | =9.0.0-milestone24 | |
Apache Tomcat | =9.0.0-milestone25 | |
Apache Tomcat | =9.0.0-milestone26 | |
Apache Tomcat | =9.0.0-milestone27 | |
Apache Tomcat | =9.0.0-milestone9 | |
maven/org.apache.tomcat.embed:tomcat-embed-core | >=9.0.0.M9<9.0.10 | 9.0.10 |
maven/org.apache.tomcat.embed:tomcat-embed-core | >=8.5.5<8.5.32 | 8.5.32 |
redhat/tomcat | <8.5.32 | 8.5.32 |
redhat/tomcat | <9.0.10 | 9.0.10 |
redhat/tomcat | <7.0.87 | 7.0.87 |
>=8.5.5<=8.5.31 | ||
>=9.0.1<=9.0.9 | ||
=9.0.0 | ||
=9.0.0-milestone10 | ||
=9.0.0-milestone11 | ||
=9.0.0-milestone12 | ||
=9.0.0-milestone13 | ||
=9.0.0-milestone14 | ||
=9.0.0-milestone15 | ||
=9.0.0-milestone16 | ||
=9.0.0-milestone17 | ||
=9.0.0-milestone18 | ||
=9.0.0-milestone19 | ||
=9.0.0-milestone20 | ||
=9.0.0-milestone21 | ||
=9.0.0-milestone22 | ||
=9.0.0-milestone23 | ||
=9.0.0-milestone24 | ||
=9.0.0-milestone25 | ||
=9.0.0-milestone26 | ||
=9.0.0-milestone27 | ||
=9.0.0-milestone9 | ||
=9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
CVE-2018-8037 is a vulnerability in Apache Tomcat that could result in a race condition and allow a user to see a response intended for a different user.
CVE-2018-8037 has a severity rating of 9.1, which is considered critical.
Apache Tomcat versions 8.5.32 to 8.5.31 and versions 9.0.10 to 9.0.9 are affected by CVE-2018-8037.
To fix CVE-2018-8037, update to Apache Tomcat version 8.5.32 or 9.0.10 or later.
You can find more information about CVE-2018-8037 on the Apache Tomcat official website and in the provided references.