Apache Tomcat: Failure during request clean-up leads to sensitive data leaking to subsequent requests
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat Maven |
|
|
| org.apache.tomcat.embed:tomcat-embed-core Maven |
|
|
| org.apache.tomcat:tomcat-catalina Maven |
|
|
| org.apache.tomcat:tomcat-util Maven |
|
|
Incomplete Cleanup vulnerability in Apache Tomcat.When recycling various internal objects in Apache Tomcat from 11.0.0-M1 through 11.0.0-M11, from 10.1.0-M1 through 10.1.13, from 9.0.0-M1 through 9.0.80 and from 8.5.0 through 8.5.93, an error could cause Tomcat to skip some parts of the recycling process leading to information leaking from the current request/response to the next. Older, EOL versions may also be affected.
Users are recommended to upgrade to version 11.0.0-M12 onwards, 10.1.14 onwards, 9.0.81 onwards or 8.5.94 onwards, which fixes the issue.
From the CVE record · apache
An error while recycling internal objects in Apache Tomcat can skip part of the cleanup process. This can leak information from one request or response to the next. The input does not specify whether authentication or user interaction is required.
Teams running Apache Tomcat or the affected Maven packages in the 11.0.0-M1–11.0.0-M11, 10.1.0-M1–10.1.13, 9.0.0-M1–9.0.80, or 8.5.0–8.5.93 ranges should check their versions; older end-of-life versions may also be affected.