Skip to content

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

High severity GitHub Reviewed Published Feb 9, 2022 to the GitHub Advisory Database • Updated Mar 21, 2024

Package

maven org.apache.tomcat:tomcat-coyote (Maven)

Affected versions

>= 10.0.0-M1, < 10.0.0-M10
>= 9.0.0-M1, < 9.0.40
>= 8.5.0, < 8.5.60

Patched versions

10.0.0-M10
9.0.40
8.5.60

Description

While investigating bug 64830 it was discovered that Apache Tomcat 10.0.0-M1 to 10.0.0-M9, 9.0.0-M1 to 9.0.39 and 8.5.0 to 8.5.59 could re-use an HTTP request header value from the previous stream received on an HTTP/2 connection for the request associated with the subsequent stream. While this would most likely lead to an error and the closure of the HTTP/2 connection, it is possible that information could leak between requests.

References

Published by the National Vulnerability Database Dec 3, 2020
Reviewed Apr 12, 2021
Published to the GitHub Advisory Database Feb 9, 2022
Last updated Mar 21, 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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.290%
(70th percentile)

Weaknesses

CVE ID

CVE-2020-17527

GHSA ID

GHSA-vvw4-rfwf-p6hx

Source code

Credits

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