CVE-2022-42252: Apache Tomcat request smuggling via malformed content-length

Published Nov 1, 2022
·
Updated

Apache Tomcat is vulnerable to HTTP request smuggling, caused by the failure to reject a request containing an invalid Content-Length header when configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false. By sending a specially-crafted request, an attacker could exploit this vulnerability to poison the web cache, bypass web application firewall protection, and conduct XSS attacks.

Other sources

If Apache Tomcat 8.5.0 to 8.5.52, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

https://lists.apache.org/thread/zzcxzvqfdqn515zfs3dxb7n8gty589sq

— Red Hat

If Apache Tomcat 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26 or 10.1.0-M1 to 10.1.0 was configured to ignore invalid HTTP headers via setting rejectIllegalHeader to false (the default for 8.5.x only), Tomcat did not reject a request containing an invalid Content-Length header making a request smuggling attack possible if Tomcat was located behind a reverse proxy that also failed to reject the request with the invalid header.

— Ubuntu

Affected Software

24 affected componentsFixes available
maven/org.apache.tomcat:tomcat-coyote>=10.1.0-M1<10.1.1
10.1.1
maven/org.apache.tomcat:tomcat-coyote>=10.0.0-M1<10.0.27
10.0.27
maven/org.apache.tomcat:tomcat-coyote>=9.0.0-M1<9.0.68
9.0.68
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.1.0-M1<10.1.1
10.1.1
maven/org.apache.tomcat.embed:tomcat-embed-core>=10.0.0-M1<10.0.27
10.0.27
maven/org.apache.tomcat.embed:tomcat-embed-core>=9.0.0-M1<9.0.68
9.0.68
maven/org.apache.tomcat.embed:tomcat-embed-core>=8.5.0<8.5.83
8.5.83
redhat/tomcat<10.1.1
10.1.1
redhat/tomcat<10.0.27
10.0.27
redhat/tomcat<9.0.68
9.0.68
redhat/tomcat<8.5.83
8.5.83
debian/tomcat9
9.0.43-2~deb11u109.0.70-2
ubuntu/tomcat8<8.5.39-1ubuntu1~18.04.3+
8.5.39-1ubuntu1~18.04.3+
ubuntu/tomcat8<8.5.82
8.5.82
ubuntu/tomcat9<9.0.16-3ubuntu0.18.04.2+
9.0.16-3ubuntu0.18.04.2+
ubuntu/tomcat9<9.0.31-1ubuntu0.5
9.0.31-1ubuntu0.5
ubuntu/tomcat9<9.0.58-1ubuntu0.1+
9.0.58-1ubuntu0.1+
ubuntu/tomcat9<9.0.68
9.0.68
IBM IBM® Engineering Requirements Management DOORS<=9.7.2.7
IBM IBM® Engineering Requirements Management DOORS Web Access<=9.7.2.7
Apache Tomcat>=8.5.0<8.5.83
Apache Tomcat>=9.0.0<9.0.68
Apache Tomcat>=10.0.0<10.0.27
Apache Tomcat>=10.1.0<10.1.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-coyote to a version that resolves this vulnerability.

    Fixed in 10.1.1
  2. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-coyote to a version that resolves this vulnerability.

    Fixed in 10.0.27
  3. Upgrade

    Upgrade maven/org.apache.tomcat:tomcat-coyote to a version that resolves this vulnerability.

    Fixed in 9.0.68
  4. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 10.1.1
  5. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 10.0.27
  6. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 9.0.68
  7. Upgrade

    Upgrade maven/org.apache.tomcat.embed:tomcat-embed-core to a version that resolves this vulnerability.

    Fixed in 8.5.83
  8. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.1
  9. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 10.0.27
  10. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.68
  11. Upgrade

    Upgrade redhat/tomcat to a version that resolves this vulnerability.

    Fixed in 8.5.83
  12. Upgrade

    Upgrade debian/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.43-2~deb11u10Fixed in 9.0.70-2
  13. Upgrade

    Upgrade ubuntu/tomcat8 to a version that resolves this vulnerability.

    Fixed in 8.5.39-1ubuntu1~18.04.3+
  14. Upgrade

    Upgrade ubuntu/tomcat8 to a version that resolves this vulnerability.

    Fixed in 8.5.82
  15. Upgrade

    Upgrade ubuntu/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.16-3ubuntu0.18.04.2+
  16. Upgrade

    Upgrade ubuntu/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.31-1ubuntu0.5
  17. Upgrade

    Upgrade ubuntu/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.58-1ubuntu0.1+
  18. Upgrade

    Upgrade ubuntu/tomcat9 to a version that resolves this vulnerability.

    Fixed in 9.0.68
  19. Configuration

    Set rejectIllegalHeader to true so Tomcat rejects requests with invalid Content-Length headers (the vulnerability occurs when rejectIllegalHeader is false).

    Apache Tomcat rejectIllegalHeader = true

Event History

Nov 1, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·12:00 PM
Jul 9, 2024
Data Sourced
via Launchpad·03:29 AM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID for this Apache Tomcat vulnerability?

The vulnerability ID for this Apache Tomcat vulnerability is CVE-2022-42252.

2

What is the severity of CVE-2022-42252?

The severity of CVE-2022-42252 is high with a CVSS score of 7.5.

3

Which versions of Apache Tomcat are affected by CVE-2022-42252?

Apache Tomcat versions 8.5.0 to 8.5.82, 9.0.0-M1 to 9.0.67, 10.0.0-M1 to 10.0.26, and 10.1.0-M1 to 10.1.0 are affected by CVE-2022-42252.

4

How can I fix CVE-2022-42252?

To fix CVE-2022-42252, upgrade your Apache Tomcat installation to version 8.5.83, 9.0.68, 10.0.27, or 10.1.1 depending on the version you are using.

5

Are there any references related to CVE-2022-42252?

Yes, you can find more information about CVE-2022-42252 from the following references: - [NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-42252) - [Apache Tomcat Mailing List](https://lists.apache.org/thread/zzcxzvqfdqn515zfs3dxb7n8gty589sq) - [Gentoo Security Advisory](https://security.gentoo.org/glsa/202305-37)

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203