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.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-2495-1 | tomcat8 security update |
![]() |
DSA-4835-1 | tomcat9 security update |
![]() |
EUVD-2022-1215 | 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. |
![]() |
GHSA-vvw4-rfwf-p6hx | Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat |
![]() |
USN-5360-1 | Tomcat vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: apache
Published:
Updated: 2025-02-13T16:27:36.405Z
Reserved: 2020-08-12T00:00:00.000Z
Link: CVE-2020-17527

No data.

Status : Modified
Published: 2020-12-03T19:15:12.200
Modified: 2024-11-21T05:08:17.910
Link: CVE-2020-17527


No data.