CVE-2005-2090: XSS

Published Jun 6, 2005
·
Updated

From http://tomcat.apache.org/security-5.html

Fixed in Apache Tomcat 5.5.23

Information disclosure CVE-2005-2090

Requests with multiple content-length headers should be rejected as invalid. When multiple components (firewalls, caches, proxies and Tomcat) process a sequence of requests where one or more requests contain multiple content-length headers and several components do not reject the request and make different decisions as to which content-length leader to use an attacker can poision a web-cache, perform an XSS attack and obtain senstive information from requests other then their own. Tomcat now returns 400 for requests with multiple content-length headers.

Affects: 5.0.0-5.0.HEAD, 5.5.0-5.5.22

Other sources

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."

Affected Software

25 affected componentsFixes available
maven/org.apache.tomcat:tomcat>=4.0.0<=4.1.24
maven/org.apache.tomcat:tomcat>=5.0.0<=5.0.19
redhat/pcsc-lite<0:1.3.3-3.el4
0:1.3.3-3.el4
redhat/rhpki-ca<0:7.3.0-20.el4
0:7.3.0-20.el4
redhat/rhpki-java-tools<0:7.3.0-10.el4
0:7.3.0-10.el4
redhat/rhpki-kra<0:7.3.0-14.el4
0:7.3.0-14.el4
redhat/rhpki-manage<0:7.3.0-19.el4
0:7.3.0-19.el4
redhat/rhpki-native-tools<0:7.3.0-6.el4
0:7.3.0-6.el4
redhat/rhpki-ocsp<0:7.3.0-13.el4
0:7.3.0-13.el4
redhat/rhpki-tks<0:7.3.0-13.el4
0:7.3.0-13.el4
redhat/jakarta-commons-modeler<0:1.1-8jpp.1.0.2.el5
0:1.1-8jpp.1.0.2.el5
redhat/tomcat5<0:5.5.23-0jpp.1.0.3.el5
0:5.5.23-0jpp.1.0.3.el5
redhat/java<1.4.2-ibm-0:1.4.2.10-1jpp.2.el4
1.4.2-ibm-0:1.4.2.10-1jpp.2.el4
redhat/rhn-apache<0:1.3.27-36.rhn.rhel4
0:1.3.27-36.rhn.rhel4
redhat/rhn-modjk<0:1.2.23-2rhn.rhel4
0:1.2.23-2rhn.rhel4
redhat/rhn-modperl<0:1.29-16.rhel4
0:1.29-16.rhel4
redhat/rhn-modssl<0:2.8.12-8.rhn.10.rhel4
0:2.8.12-8.rhn.10.rhel4
redhat/java<1.4.2-ibm-0:1.4.2.10-1jpp.2.el3
1.4.2-ibm-0:1.4.2.10-1jpp.2.el3
redhat/rhn-apache<0:1.3.27-36.rhn.rhel3
0:1.3.27-36.rhn.rhel3
redhat/rhn-modjk<0:1.2.23-2rhn.rhel3
0:1.2.23-2rhn.rhel3
redhat/rhn-modperl<0:1.29-16.rhel3
0:1.29-16.rhel3
redhat/rhn-modssl<0:2.8.12-8.rhn.10.rhel3
0:2.8.12-8.rhn.10.rhel3
redhat/jbossas<0:4.0.5-2.CP04.el4
0:4.0.5-2.CP04.el4
Tomcat=4.1.24
Tomcat=5.0.19

Event History

Jun 6, 2005
CVE Published
via Red Hat·12:00 AM
Jun 30, 2005
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Apr 19, 2007
Data Sourced
via Red Hat·11:50 AM
DescriptionSeverityAffected Software
May 1, 2022
Advisory Published
02:04 AM

Frequently Asked Questions

1

What is the severity of CVE-2005-2090?

The severity of CVE-2005-2090 is classified as high due to its potential for remote exploitation.

2

How do I fix CVE-2005-2090?

To fix CVE-2005-2090, upgrade to Apache Tomcat version 5.0.20 or later, or 4.1.25 or later.

3

Which versions of Tomcat are affected by CVE-2005-2090?

CVE-2005-2090 affects Apache Tomcat versions 4.1.24 and earlier, as well as 5.0.19 and earlier.

4

What type of attacks can CVE-2005-2090 facilitate?

CVE-2005-2090 can facilitate web cache poisoning, bypassing web application firewalls, and cross-site scripting (XSS) attacks.

5

Is CVE-2005-2090 related to any other vulnerabilities?

Yes, CVE-2005-2090 shares similarities with other vulnerabilities that exploit improper input processing in web applications.

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