CVE-2016-8745
Last modified
CVE-2016-8745 is a vulnerability of currently unknown severity. 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. EPSS estimates a 16.04% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| 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 | — |
Showing 50 of 123 affected configurations. See NVD for the full list.
References
- http://www.securityfocus.com/bid/94828Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037432Third Party Advisory, VDB Entry
- https://security.gentoo.org/glsa/201705-09Third Party Advisory, VDB Entry
- http://www.securityfocus.com/bid/94828Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037432Third Party Advisory, VDB Entry
- https://security.gentoo.org/glsa/201705-09Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-8745?
How severe is CVE-2016-8745?
How do I fix CVE-2016-8745?
Are you affected by CVE-2016-8745?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST