CVE-2018-8037: Race Condition

Published Jul 22, 2018
·
Updated

Flaw affecting tomcat 9.0.0.M9 to 9.0.9 and 8.5.5 to 8.5.31. A bug in the tracking of connection closures can lead to reuse of user sessions in a new connection.

Upstream patch:

http://svn.apache.org/viewvc?view=rev&rev=1833906 http://svn.apache.org/viewvc?view=rev&rev=1833907

References:

https://tomcat.apache.org/security-8.html https://tomcat.apache.org/security-9.html

Other sources

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 Software

50 affected componentsFixes available
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~deb10u69.0.31-1~deb10u109.0.43-2~deb11u69.0.43-2~deb11u99.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
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-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
Debian Debian Linux=9.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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.7-12.redhat_12.1.el6
  2. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.7-12.redhat_12.1.el7
  3. Upgrade

    Upgrade debian/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.31-1~deb10u6Fixed in 9.0.31-1~deb10u10Fixed in 9.0.43-2~deb11u6Fixed in 9.0.43-2~deb11u9Fixed in 9.0.70-2
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.10
  5. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.5.32
  6. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.32
  7. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.10
  8. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 7.0.87
  9. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.9
  10. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.31

Event History

Jul 22, 2018
CVE Published
12:00 AM
Jul 23, 2018
Data Sourced
via Red Hat·07:23 PM
DescriptionSeverityAffected Software
Aug 2, 2018
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
DescriptionWeakness
Oct 17, 2018
Advisory Published
via GitHub·04:33 PM

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

What is the severity of CVE-2018-8037?

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

3

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.

4

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.

5

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.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203