CVE-2017-5647

A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.

TuxCare rebuilt 32 packages to address 16 CVEs. Fixed in 7.0.70-tuxcare.4.

A bug in the handling of the pipelined requests when send file was used resulted in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C (CVE-2017-5647).

While investigating bug 60718, it was noticed that some calls to application listeners did not use the appropriate facade object. When running an untrusted application under a SecurityManager, it was therefore possible for that untrusted application to retain a reference to the request or response object and thereby access and/or modify information associated with another web application (CVE-2017-5648).

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 Tomcat incorrectly handled certain pipelined requests when sendfile was used. A remote attacker could use this issue to obtain wrong responses possibly containing sensitive information. (CVE-2017-5647)

It was discovered that Tomcat incorrectly used the appropriate facade object. A malicious application could possibly use this to bypass Security Manager restrictions. (CVE-2017-5648)

It was discovered that Tomcat incorrectly handled error pages. A remote attacker could possibly use this issue to replace or remove the custom error page. (CVE-2017-5664)

It was discovered that Tomcat incorrectly handled the CORS filter. A remote attacker could possibly use this issue to perform cache poisoning. (CVE-2017-7674)