CVE-2005-2090

UnknownEPSS 29.78%

Last modified

CVE-2005-2090 is a vulnerability of currently unknown severity. Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling.". EPSS estimates a 29.78% chance of exploitation in the next 30 days.

Description

Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling."

Metrics

EPSS Probability
29.78%

98.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
ApacheTomcat4.1.24
ApacheTomcat5.0.19

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2005-2090?
Jakarta Tomcat 5.0.19 (Coyote/1.1) and Tomcat 4.1.24 (Coyote/1.0) allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling."
How severe is CVE-2005-2090?
Severity scoring for CVE-2005-2090 is pending analysis. The EPSS model estimates a 29.78% probability of exploitation in the next 30 days.
How do I fix CVE-2005-2090?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2005-2090?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST