high
7.5
CWE
362 388
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2016-8745: Race Condition

First published: Mon Dec 12 2016(Updated: )

A bug in the error handling of the send file code for the NIO HTTP connector in Apache Tomcat 9.0.0.M1 to 9.0.0.M13, 8.5.0 to 8.5.8, 8.0.0.RC1 to 8.0.39, 7.0.0 to 7.0.73 and 6.0.16 to 6.0.48 resulted in the current Processor object being added to the Processor cache multiple times. This in turn meant that the same Processor could be used for concurrent requests. Sharing a Processor can result in information leakage between requests including, not not limited to, session ID and the response body. The bug was first noticed in 8.5.x onwards where it appears the refactoring of the Connector code for 8.5.x onwards made it more likely that the bug was observed. Initially it was thought that the 8.5.x refactoring introduced the bug but further investigation has shown that the bug is present in all currently supported Tomcat versions.

Credit: security@apache.org security@apache.org security@apache.org

Affected SoftwareAffected VersionHow to fix
Apache Tomcat=7.0.0
Apache Tomcat=7.0.1
Apache Tomcat=7.0.2
Apache Tomcat=7.0.3
Apache Tomcat=7.0.4
Apache Tomcat=7.0.5
Apache Tomcat=7.0.6
Apache Tomcat=7.0.7
Apache Tomcat=7.0.8
Apache Tomcat=7.0.9
Apache Tomcat=7.0.11
Apache Tomcat=7.0.12
Apache Tomcat=7.0.13
Apache Tomcat=7.0.14
Apache Tomcat=7.0.15
Apache Tomcat=7.0.16
Apache Tomcat=7.0.17
Apache Tomcat=7.0.18
Apache Tomcat=7.0.19
Apache Tomcat=7.0.20
Apache Tomcat=7.0.21
Apache Tomcat=7.0.22
Apache Tomcat=7.0.23
Apache Tomcat=7.0.24
Apache Tomcat=7.0.25
Apache Tomcat=7.0.26
Apache Tomcat=7.0.27
Apache Tomcat=7.0.28
Apache Tomcat=7.0.29
Apache Tomcat=7.0.30
Apache Tomcat=7.0.31
Apache Tomcat=7.0.32
Apache Tomcat=7.0.33
Apache Tomcat=7.0.34
Apache Tomcat=7.0.35
Apache Tomcat=7.0.36
Apache Tomcat=7.0.37
Apache Tomcat=7.0.38
Apache Tomcat=7.0.39
Apache Tomcat=7.0.40
Apache Tomcat=7.0.41
Apache Tomcat=7.0.42
Apache Tomcat=7.0.43
Apache Tomcat=7.0.44
Apache Tomcat=7.0.45
Apache Tomcat=7.0.46
Apache Tomcat=7.0.47
Apache Tomcat=7.0.48
Apache Tomcat=7.0.49
Apache Tomcat=7.0.50
Apache Tomcat=7.0.52
Apache Tomcat=7.0.53
Apache Tomcat=7.0.54
Apache Tomcat=7.0.55
Apache Tomcat=7.0.56
Apache Tomcat=7.0.57
Apache Tomcat=7.0.58
Apache Tomcat=7.0.59
Apache Tomcat=7.0.60
Apache Tomcat=7.0.61
Apache Tomcat=7.0.62
Apache Tomcat=7.0.63
Apache Tomcat=7.0.64
Apache Tomcat=7.0.65
Apache Tomcat=7.0.66
Apache Tomcat=7.0.67
Apache Tomcat=7.0.68
Apache Tomcat=7.0.69
Apache Tomcat=7.0.70
Apache Tomcat=7.0.71
Apache Tomcat=7.0.72
Apache Tomcat=7.0.73
Apache Tomcat=8.0
Apache Tomcat=8.0.0-rc1
Apache Tomcat=8.0.0-rc10
Apache Tomcat=8.0.0-rc3
Apache Tomcat=8.0.0-rc5
Apache Tomcat=8.0.1
Apache Tomcat=8.0.2
Apache Tomcat=8.0.3
Apache Tomcat=8.0.4
Apache Tomcat=8.0.5
Apache Tomcat=8.0.6
Apache Tomcat=8.0.7
Apache Tomcat=8.0.8
Apache Tomcat=8.0.9
Apache Tomcat=8.0.10
Apache Tomcat=8.0.11
Apache Tomcat=8.0.12
Apache Tomcat=8.0.13
Apache Tomcat=8.0.14
Apache Tomcat=8.0.15
Apache Tomcat=8.0.16
Apache Tomcat=8.0.17
Apache Tomcat=8.0.18
Apache Tomcat=8.0.19
Apache Tomcat=8.0.20
Apache Tomcat=8.0.21
Apache Tomcat=8.0.22
Apache Tomcat=8.0.23
Apache Tomcat=8.0.24
Apache Tomcat=8.0.25
Apache Tomcat=8.0.26
Apache Tomcat=8.0.27
Apache Tomcat=8.0.28
Apache Tomcat=8.0.29
Apache Tomcat=8.0.30
Apache Tomcat=8.0.31
Apache Tomcat=8.0.32
Apache Tomcat=8.0.33
Apache Tomcat=8.0.34
Apache Tomcat=8.0.35
Apache Tomcat=8.0.36
Apache Tomcat=8.0.37
Apache Tomcat=8.0.38
Apache Tomcat=8.0.39
Apache Tomcat=8.5.0
Apache Tomcat=8.5.1
Apache Tomcat=8.5.2
Apache Tomcat=8.5.3
Apache Tomcat=8.5.4
Apache Tomcat=8.5.5
Apache Tomcat=8.5.6
Apache Tomcat=8.5.7
Apache Tomcat=8.5.8
Apache Tomcat=9.0.0-m1
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-m2
Apache Tomcat=9.0.0-m3
Apache Tomcat=9.0.0-m4
Apache Tomcat=9.0.0-m5
Apache Tomcat=9.0.0-m6
Apache Tomcat=9.0.0-m7
Apache Tomcat=9.0.0-m8
Apache Tomcat=9.0.0-m9
Apache Tomcat=9.0.0-milestone1
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-milestone2
Apache Tomcat=9.0.0-milestone3
Apache Tomcat=9.0.0-milestone4
Apache Tomcat=9.0.0-milestone5
Apache Tomcat=9.0.0-milestone6
Apache Tomcat=9.0.0-milestone7
Apache Tomcat=9.0.0-milestone8
Apache Tomcat=9.0.0-milestone9
redhat/tomcat<8.5.9
8.5.9
redhat/tomcat<9.0.0.
9.0.0.
redhat/tomcat<6.0.50
6.0.50
redhat/tomcat<7.0.75
7.0.75
redhat/tomcat<8.0.41
8.0.41
maven/org.apache.tomcat:tomcat>=6.0.16<6.0.50
6.0.50
maven/org.apache.tomcat:tomcat>=7.0.0<7.0.75
7.0.75
maven/org.apache.tomcat:tomcat>=8.0.0RC1<8.0.41
8.0.41
maven/org.apache.tomcat:tomcat>=8.5.0<=8.5.8
8.5.9
maven/org.apache.tomcat:tomcat>=9.0.0.M1<=9.0.0.M13
9.0.0.M14
debian/tomcat9
9.0.43-2~deb11u10
9.0.43-2~deb11u11
9.0.70-2
9.0.95-1

Remedy

http://svn.apache.org/viewvc?view=revision&revision=1777471

Remedy

http://svn.apache.org/viewvc?view=revision&revision=1777469

Remedy

http://svn.apache.org/viewvc?view=revision&revision=1777472

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

Frequently Asked Questions

  • What is the severity of CVE-2016-8745?

    CVE-2016-8745 is rated as a medium-severity vulnerability with potential impacts on performance and resource management in affected Apache Tomcat versions.

  • How do I fix CVE-2016-8745?

    To resolve CVE-2016-8745, upgrade to the patched versions of Apache Tomcat: 6.0.50, 7.0.75, 8.0.41, 8.5.9, or 9.0.0.M14.

  • Which versions of Apache Tomcat are affected by CVE-2016-8745?

    CVE-2016-8745 affects Apache Tomcat versions 6.0.16 to 6.0.48, 7.0.0 to 7.0.73, 8.0.0-rc1 to 8.0.39, and 8.5.0 to 8.5.8.

  • What potential impact does CVE-2016-8745 have on Apache Tomcat?

    CVE-2016-8745 may lead to multiple instances of the same Processor object being cached, potentially leading to performance degradation.

  • Is there a workaround for CVE-2016-8745, or is an update required?

    While upgrading to the latest secure version is recommended, there are no documented workarounds to mitigate the effects of CVE-2016-8745.

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