Homepage

Information Exposure Affecting tomcat6-servlet-2.5-api package, versions <0:6.0.24-111.el6_9

Severity

 Recommended
0.0
high
0
10

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.28% (69th 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-ORACLE6-TOMCAT6SERVLET25API-2517652
  • published10 Apr 2022
  • disclosed17 Apr 2017
Report a new vulnerability Found a mistake?

Introduced: 17 Apr 2017

CVE-2017-5647  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade Oracle:6 tomcat6-servlet-2.5-api to version 0:6.0.24-111.el6_9 or higher.
This issue was patched in ELSA-2017-3080.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat6-servlet-2.5-api package and not the tomcat6-servlet-2.5-api package as distributed by Oracle. See How to fix? for Oracle:6 relevant fixed versions and status.

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.

References