Bug 457597 (CVE-2008-1232) - CVE-2008-1232 tomcat: Cross-Site-Scripting enabled by sendError call
Summary: CVE-2008-1232 tomcat: Cross-Site-Scripting enabled by sendError call
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2008-1232
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://tomcat.apache.org/security-6.html
Whiteboard:
Depends On: 457727 457728 458088 458089 458097 458099 458100 458443 458444 458445 460125 460126 460127 460131 460132 470238 470239
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-01 18:09 UTC by Marc Schoenefeld
Modified: 2019-09-29 12:26 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-03 06:55:38 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0648 0 normal SHIPPED_LIVE Important: tomcat security update 2008-08-27 17:13:49 UTC
Red Hat Product Errata RHSA-2008:0862 0 normal SHIPPED_LIVE Important: tomcat security update 2008-10-02 14:03:32 UTC
Red Hat Product Errata RHSA-2008:0864 0 normal SHIPPED_LIVE Important: tomcat security update 2008-10-02 14:02:59 UTC
Red Hat Product Errata RHSA-2008:1007 0 normal SHIPPED_LIVE Low: tomcat security update for Red Hat Network Satellite Server 2008-12-08 09:02:54 UTC
Red Hat Product Errata RHSA-2010:0602 0 normal SHIPPED_LIVE Moderate: Red Hat Certificate System 7.3 security update 2010-08-05 14:04:51 UTC

Description Marc Schoenefeld 2008-08-01 18:09:20 UTC
The message argument of HttpServletResponse.sendError() call is not only
displayed on the error page, but is also used for the reason-phrase of HTTP
response. This may include characters that are illegal in HTTP headers. It is
possible for a specially crafted message to result in arbitrary content being
injected into the HTTP response. For a successful XSS attack, unfiltered user
supplied data must be included in the message argument.

Comment 1 Tomas Hoger 2008-08-04 06:29:11 UTC
Public now via: http://tomcat.apache.org/security-6.html

Comment 2 Tomas Hoger 2008-08-04 06:48:02 UTC
Also affects older Tomcat versions:
  http://tomcat.apache.org/security-5.html
  http://tomcat.apache.org/security-4.html

Comment 4 Marc Schoenefeld 2008-08-04 16:02:11 UTC
Patch available here:

http://svn.apache.org/viewvc?rev=680947&view=rev

Comment 12 Fedora Update System 2008-09-05 17:10:49 UTC
tomcat6-6.0.18-1.1.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/tomcat6-6.0.18-1.1.fc9

Comment 13 Fedora Update System 2008-09-11 17:17:32 UTC
tomcat6-6.0.18-1.1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2008-09-15 18:12:12 UTC
tomcat5-5.5.27-0jpp.1.fc8 has been submitted as an update for Fedora 8.
http://admin.fedoraproject.org/updates/tomcat5-5.5.27-0jpp.1.fc8

Comment 15 Fedora Update System 2008-09-15 20:13:49 UTC
tomcat5-5.5.27-0jpp.2.fc9 has been submitted as an update for Fedora 9.
http://admin.fedoraproject.org/updates/tomcat5-5.5.27-0jpp.2.fc9

Comment 16 Fedora Update System 2008-09-15 20:16:21 UTC
tomcat5-5.5.27-0jpp.2.fc8 has been submitted as an update for Fedora 8.
http://admin.fedoraproject.org/updates/tomcat5-5.5.27-0jpp.2.fc8

Comment 17 Fedora Update System 2008-09-16 23:24:51 UTC
tomcat5-5.5.27-0jpp.2.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 18 Fedora Update System 2008-09-16 23:28:18 UTC
tomcat5-5.5.27-0jpp.2.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 21 errata-xmlrpc 2010-08-04 21:31:09 UTC
This issue has been addressed in following products:

  Red Hat Certificate System 7.3

Via RHSA-2010:0602 https://rhn.redhat.com/errata/RHSA-2010-0602.html


Note You need to log in before you can comment on or make changes to this bug.