CVE-2016-8745

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.

TuxCare rebuilt 7 packages to address 11 CVEs. Fixed in 7.0.70-tuxcare.3.

It was discovered that incorrect error handling in the NIO HTTP connector of the Tomcat servlet and JSP engine could result in information disclosure (CVE-2016-8745).

These are all security issues fixed in the tomcat-9.0.36-8.4 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the tomcat10-10.1.14-1.1 package on the GA media of openSUSE Tumbleweed.

This update for tomcat fixes the following issues:

• CVE-2017-5647 Pipelined requests could lead to information disclosure (bsc#1033448)
• CVE-2017-5648 Untrusted application could retain listener leading to information disclosure (bsc#1033447)
• CVE-2016-8745 shared Processor on Connector code could lead to information disclosure (bsc#1015119)

This update for tomcat fixes the following issues:

• CVE-2017-5647 Pipelined requests could lead to information disclosure (bsc#1033448)
• CVE-2017-5648 Untrusted application could retain listener leading to information disclosure (bsc#1033447)
• CVE-2016-8745 shared Processor on Connector code could lead to information disclosure (bsc#1015119)

This update for tomcat6 fixes the following issues:

Tomcat was updated to version 6.0.53:

The full changelog is: http://tomcat.apache.org/tomcat-6.0-doc/changelog.html

Security issues fixed:

• CVE-2017-5647: A bug in the handling of pipelined requests could lead to information disclosure (bsc#1036642)
• CVE-2016-8745: Regression in the error handling methods could lead to information disclosure (bsc#1015119)
• CVE-2016-8735: Remote code execution vulnerability in JmxRemoteLifecycleListener (bsc#1011805)
• CVE-2016-6816: HTTP Request smuggling vulnerability due to permitting invalid character in HTTP requests (bsc#1011812)
• CVE-2016-6797: Unrestricted Access to Global Resources (bsc#1007853)
• CVE-2016-6796: Manager Bypass (bsc#1007858)
• CVE-2016-6794: System Property Disclosure (bsc#1007857)
• CVE-2016-5018: Security Manager Bypass (bsc#1007855)
• CVE-2016-0762: Realm Timing Attack (bsc#1007854)
• CVE-2016-5388: an arbitrary HTTP_PROXY environment variable might allow remote attackers to redirect outbound HTTP traffic (bsc#988489)

Tomcat was updated to version 7.0.78, fixing various bugs and security issues.

For full details see https://tomcat.apache.org/tomcat-7.0-doc/changelog.html

Security issues fixed:

• CVE-2016-0762: A realm timing attack in tomcat was fixed which could disclose existence of users (bsc#1007854)
• CVE-2016-3092: Usage of vulnerable FileUpload package could have resulted in denial of service (bsc#986359)
• CVE-2016-5018: A security manager bypass via a Tomcat utility method that was accessible to web applications was fixed. (bsc#1007855)
• CVE-2016-5388: Setting HTTP_PROXY environment variable via Proxy header (bsc#988489)
• CVE-2016-6794: A tomcat system property disclosure was fixed. (bsc#1007857)
• CVE-2016-6796: A tomcat security manager bypass via manipulation of the configuration parameters for the JSP Servlet. (bsc#1007858)
• CVE-2016-6797: A tomcat unrestricted access to global resources via ResourceLinkFactory was fixed. (bsc#1007853)
• CVE-2016-6816: A HTTP Request smuggling vulnerability due to permitting invalid character in HTTP requests was fixed. (bsc#1011812)
• CVE-2016-8735: A Remote code execution vulnerability in JmxRemoteLifecycleListener was fixed (bsc#1011805)
• CVE-2016-8745: A Tomcat Information Disclosure in the error handling of send file code for the NIO HTTP connector was fixed. (bsc#1015119)
• CVE-2017-5647: A tomcat information disclosure in pipelined request processing was fixed. (bsc#1033448)
• CVE-2017-5648: A tomcat information disclosure due to using incorrect facade objects was fixed (bsc#1033447)

It was discovered that the Tomcat realm implementations incorrectly handled passwords when a username didn't exist. A remote attacker could possibly use this issue to enumerate usernames. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-0762)

Alvaro Munoz and Alexander Mirosh discovered that Tomcat incorrectly limited use of a certain utility method. A malicious application could possibly use this to bypass Security Manager restrictions. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-5018)

It was discovered that Tomcat did not protect applications from untrusted data in the HTTP_PROXY environment variable. A remote attacker could possibly use this issue to redirect outbound traffic to an arbitrary proxy server. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-5388)

It was discovered that Tomcat incorrectly controlled reading system properties. A malicious application could possibly use this to bypass Security Manager restrictions. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-6794)

It was discovered that Tomcat incorrectly controlled certain configuration parameters. A malicious application could possibly use this to bypass Security Manager restrictions. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-6796)

It was discovered that Tomcat incorrectly limited access to global JNDI resources. A malicious application could use this to access any global JNDI resource without an explicit ResourceLink. This issue only applied to Ubuntu 12.04 LTS, Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-6797)

Regis Leroy discovered that Tomcat incorrectly filtered certain invalid characters from the HTTP request line. A remote attacker could possibly use this issue to inject data into HTTP responses. (CVE-2016-6816)

Pierre Ernst discovered that the Tomcat JmxRemoteLifecycleListener did not implement a recommended fix. A remote attacker could possibly use this issue to execute arbitrary code. (CVE-2016-8735)

It was discovered that Tomcat incorrectly handled error handling in the send file code. A remote attacker could possibly use this issue to access information from other requests. (CVE-2016-8745)

Paul Szabo discovered that the Tomcat package incorrectly handled upgrades and removals. A local attacker could possibly use this issue to obtain root privileges. (CVE-2016-9774, CVE-2016-9775)