Skip to content

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

High severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Mar 19, 2024

Package

maven org.apache.tomcat:tomcat (Maven)

Affected versions

>= 9.0.0.M1, <= 9.0.0.M18
>= 8.5.0, <= 8.5.12
>= 7.0.0, <= 7.0.76
>= 6.0.0, <= 6.0.52
>= 8.0.0, <= 8.0.42

Patched versions

9.0.0.M19
8.5.13
7.0.77
6.0.53
8.0.43

Description

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

Published by the National Vulnerability Database Apr 17, 2017
Published to the GitHub Advisory Database May 14, 2022
Reviewed Jul 1, 2022
Last updated Mar 19, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.283%
(69th percentile)

Weaknesses

CVE ID

CVE-2017-5647

GHSA ID

GHSA-3gv7-3h64-78cm

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.