Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat
Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
From the CVE record · apache
Apache Tomcat’s HTTP/2 handling can reuse headers from a previous request after a client exceeds the agreed maximum number of concurrent streams on a connection. Subsequent requests on that connection may return responses for unexpected resources, potentially exposing them to users.
Check Apache Tomcat deployments and Maven org.apache.tomcat:tomcat-coyote packages in versions 10.0.0-M1 through 10.0.0-M7, 9.0.0-M1 through 9.0.37, or 8.5.0 through 8.5.57.