Apache Tomcat h2c request mix-up
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat-coyote Maven |
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat-coyote Maven |
|
|
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
From the CVE record · apache
Apache Tomcat can duplicate request headers and a limited amount of request body between requests when responding to new h2c connections. This can let one user see the results of another user's request. The input does not specify whether authentication or user interaction is required.
Teams running Maven org.apache.tomcat.embed:tomcat-embed-core versions >=10.0.0-M1 <10.0.2, >=9.0.0-M1 <9.0.43, or >=8.5.0 <8.5.63, or org.apache.tomcat:tomcat-coyote versions >=10.0.0-M1 <10.0.2, should check their deployments.