Apache Tomcat: Request header mix-up between HTTP/2 streams
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
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.
From the CVE record · apache
Apache Tomcat can reuse an HTTP request header value from the previous stream on an HTTP/2 connection in a subsequent request, potentially leaking information between requests. The issue may instead cause an error and close the connection; authentication and user-interaction requirements are not specified.
Check Apache Tomcat or Maven org.apache.tomcat:tomcat-coyote deployments running 10.0.0-M1 through 10.0.0-M9, 9.0.0-M1 through 9.0.39, or 8.5.0 through 8.5.59.