Apache Tomcat: AJP response header 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 |
|
|
A regression in the fix for bug 66512 in Apache Tomcat 11.0.0-M5, 10.1.8, 9.0.74 and 8.5.88 meant that, if a response did not include any HTTP headers no AJP SEND_HEADERS messare woudl be sent for the response which in turn meant that at least one AJP proxy (mod_proxy_ajp) would use the response headers from the previous request leading to an information leak.
From the CVE record · apache
A regression in Apache Tomcat can cause a response with no HTTP headers to omit the AJP SEND_HEADERS message. When an affected AJP proxy such as mod_proxy_ajp handles that response, it may reuse headers from the previous request, leaking information. The input does not specify whether authentication or user interaction is required.
Check deployments using Maven tomcat-embed-core versions >=11.0.0-M5 <11.0.0-M6, >=10.1.8 <10.1.9, or >=9.0.74 <9.0.75, and tomcat-coyote versions >=8.5.88 <8.5.89.