CVE Database

CVE-2005-2090

Impact: Moderate
Public: 2005-06-06
Bugzilla: 237079: CVE-2005-2090 tomcat multiple content-length header poisioning

Details

The MITRE CVE dictionary describes this issue as:

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

Find out more about CVE-2005-2090 from the MITRE CVE dictionary and NIST NVD.

Red Hat security errata

Platform Errata Release Date
Red Hat Application Server 3AS (tomcat5) RHSA-2007:0340 May 08, 2007
Red Hat Application Server v2 4AS RHSA-2007:0326 May 21, 2007
Red Hat Application Stack v1 for Enterprise Linux AS (v.4) (jbossas) RHSA-2007:0360 May 24, 2007
Red Hat Certificate System 7.3 for 4AS RHSA-2010:0602 August 04, 2010
Red Hat Developer Suite v.3 (AS v.4) RHSA-2007:0328 May 24, 2007
Red Hat Enterprise Linux version 5 RHSA-2007:0327 May 14, 2007
Red Hat Satellite 5.0 (RHEL v.4 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite 5.0 (RHEL v.4 AS) RHSA-2008:0261 May 20, 2008
Red Hat Satellite v 4.0 (RHEL v.3 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite v 4.0 (RHEL v.4 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite v 4.1 (RHEL v.3 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite v 4.1 (RHEL v.4 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite v 4.2 (RHEL v.3 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite v 4.2 (RHEL v.3 AS) RHSA-2008:0524 June 30, 2008
Red Hat Satellite v 4.2 (RHEL v.4 AS) RHSA-2007:1069 November 26, 2007
Red Hat Satellite v 4.2 (RHEL v.4 AS) RHSA-2008:0524 June 30, 2008

External References

This page is generated automatically and has not been checked for errors or omissions.

For clarification or corrections please contact the Red Hat Security Response Team.