| Package | Affected versions | Patched versions |
|---|---|---|
| org.apache.tomcat.embed:tomcat-embed-core | ≥ 10.1.0-M1, < 10.1.55≥ 11.0.0-M1, < 11.0.22≥ 8.5.0, < 9.0.118 | 10.1.5511.0.229.0.118 |
| org.apache.tomcat:tomcat | ≥ 10.1.0-M1, < 10.1.55≥ 11.0.0-M1, < 11.0.22≥ 8.5.0, < 9.0.118 | 10.1.5511.0.229.0.118 |
| org.apache.tomcat:tomcat-coyote | ≥ 10.1.0-M1, < 10.1.55≥ 11.0.0-M1, < 11.0.22≥ 8.5.0, < 9.0.118 | 10.1.5511.0.229.0.118 |
| tomcat | ≥ 10.0.0, ≤ 10.0.27≥ 10.1.0, < 10.1.55≥ 11.0.0, < 11.0.22≥ 8.5.0, ≤ 8.5.100≥ 9.0.0, < 9.0.118 | 10.1.5511.0.229.0.118 |
Versions Affected: Apache Tomcat 11.0.0-M1 to 11.0.21 Apache Tomcat 10.1.0-M1 to 10.1.54 Apache Tomcat 9.0.0.M1 to 9.0.117 Older, unsupported versions may also be affected
Description: HTTP/2 request headers were not validated which may have triggered unexpected application behaviour if the application (quite reasonably) assumed that header value exposed through the Servlet API would be specification compliant.
Mitigation: Users of the affected versions should apply one of the following mitigations:
Credit: This issue was identified by Dawit Jeong (@dawitngoliath)
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free