Apache Tomcat request smuggling via malformed content-length
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 8.5.83, 9.0.68, 10.0.27, 10.1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Apache Software Foundation Apache Tomcat
From 10.1.0-M1 · through 10.1.0; From 10.0.0-M1 · through 10.0.26; From 9.0.0-M1 · through 9.0.67; From 8.5.0 · through 8.5.82
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 8.5.0 · fixed in 8.5.83
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 9.0.0-M1 · fixed in 9.0.68
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 10.0.0-M1 · fixed in 10.0.27
- org.apache.tomcat.embed:tomcat-embed-coreMaven
From 10.1.0-M1 · fixed in 10.1.1
- org.apache.tomcat:tomcat-coyoteMaven
From 9.0.0-M1 · fixed in 9.0.68
- org.apache.tomcat:tomcat-coyoteMaven
From 10.0.0-M1 · fixed in 10.0.27
- org.apache.tomcat:tomcat-coyoteMaven
From 10.1.0-M1 · fixed in 10.1.1