Homepage

Error Handling Affecting tomcat-el-2.2-api package, versions <0:7.0.69-11.el7_3

Severity

 Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
1.46% (87th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-TOMCATEL22API-4689931
  • published26 Jul 2021
  • disclosed12 Dec 2016
Report a new vulnerability Found a mistake?

Introduced: 12 Dec 2016

CVE-2016-8745  (opens in a new tab)
CWE-388  (opens in a new tab)

How to fix?

Upgrade RHEL:7 tomcat-el-2.2-api to version 0:7.0.69-11.el7_3 or higher.
This issue was patched in RHSA-2017:0935.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat-el-2.2-api package and not the tomcat-el-2.2-api package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

References