critical
9.1
CWE
362
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2018-8037: Race Condition

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 SoftwareAffected VersionHow 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
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
Tomcat>=8.5.5<=8.5.31
Tomcat>=9.0.1<=9.0.9
Tomcat=9.0.0
Tomcat=9.0.0-milestone10
Tomcat=9.0.0-milestone11
Tomcat=9.0.0-milestone12
Tomcat=9.0.0-milestone13
Tomcat=9.0.0-milestone14
Tomcat=9.0.0-milestone15
Tomcat=9.0.0-milestone16
Tomcat=9.0.0-milestone17
Tomcat=9.0.0-milestone18
Tomcat=9.0.0-milestone19
Tomcat=9.0.0-milestone20
Tomcat=9.0.0-milestone21
Tomcat=9.0.0-milestone22
Tomcat=9.0.0-milestone23
Tomcat=9.0.0-milestone24
Tomcat=9.0.0-milestone25
Tomcat=9.0.0-milestone26
Tomcat=9.0.0-milestone27
Tomcat=9.0.0-milestone9
Debian=9.0
Tomcat=9.0.0-m10
Tomcat=9.0.0-m11
Tomcat=9.0.0-m12
Tomcat=9.0.0-m13
Tomcat=9.0.0-m14
Tomcat=9.0.0-m15
Tomcat=9.0.0-m16
Tomcat=9.0.0-m17
Tomcat=9.0.0-m18
Tomcat=9.0.0-m19
Tomcat=9.0.0-m20
Tomcat=9.0.0-m21
Tomcat=9.0.0-m22
Tomcat=9.0.0-m23
Tomcat=9.0.0-m24
Tomcat=9.0.0-m25
Tomcat=9.0.0-m26
Tomcat=9.0.0-m27
Tomcat=9.0.0-m9

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is CVE-2018-8037?

    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.

  • What is the severity of CVE-2018-8037?

    CVE-2018-8037 has a severity rating of 9.1, which is considered critical.

  • Which versions of Apache Tomcat are affected by CVE-2018-8037?

    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.

  • How can I fix CVE-2018-8037?

    To fix CVE-2018-8037, update to Apache Tomcat version 8.5.32 or 9.0.10 or later.

  • Where can I find more information about CVE-2018-8037?

    You can find more information about CVE-2018-8037 on the Apache Tomcat official website and in the provided references.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203