Bug 71177 - Content-type not set for errors
Content-type not set for errors
Status: CLOSED ERRATA
Product: Stronghold Cross Platform
Classification: Retired
Component: tomcat (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Gary Benson
Stronghold Engineering List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-08-09 12:29 EDT by Gary Benson
Modified: 2007-04-18 12:45 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-11-07 12:41:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Script to check vulnerability (1004 bytes, text/plain)
2002-09-24 06:26 EDT, Gary Benson
no flags Details

  None (edit)
Description Gary Benson 2002-08-09 12:29:18 EDT
Tomcat 4.0.3 does not set the content-type for error messages, so exceptions are
displayed as text/plain instead of text/html when viewed through mod_webapp (the
default configuration for SH4).  This is
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6468 and was fixed in Tomcat
4.0.4.
Comment 1 Gary Benson 2002-08-09 12:33:48 EDT
Note that this bug neatly makes SH4 invulnerable to the cross-site scripting
attack detailed in http://www.westpoint.ltd.uk/advisories/wp-02-0008.txt.  This
must obviously be remedied before we fix this bug.
Comment 2 Gary Benson 2002-09-09 09:03:07 EDT
The advisory mentioned above has been classified as
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0682.
Comment 3 Gary Benson 2002-09-24 06:22:20 EDT
Even without the above bug Stronghold isn't vulnerable to the exploit in the
default configuration, but it is vulnerable if the user enables the
Tomcat-Standalone service.
Comment 4 Gary Benson 2002-09-24 06:26:33 EDT
Created attachment 77007 [details]
Script to check vulnerability
Comment 5 Gary Benson 2002-09-24 06:27:32 EDT
Note that stronghold-tomcat-4.0.3-2 (at least as we ship it) was never
vulnerable to the fourth test.
Comment 6 Gary Benson 2002-09-24 12:30:43 EDT
I was wrong when I said Stronghold is only vulnerable if the user enables the
Tomcat-Standalone service.  Replace 'http://localhost:8080/' with
'http://ServerName/stronghold/examples/java/' in the attached test script, for
example.
Comment 7 Joe Orton 2002-11-07 12:41:12 EST
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2002-218.html

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