- Issued:
- 2007-05-21
- Updated:
- 2007-05-21
RHSA-2007:0326 - Important: tomcat security update
Synopsis
Important: tomcat security update
Type/Severity
Security Advisory Important
Topic
Updated tomcat packages that fix multiple security issues are now available for Red Hat Application Server v2.
This update has been rated as having important security impact by the Red Hat Security Response Team.
Description
Tomcat is a servlet container for Java Servlet and JavaServer Pages technologies.
Tomcat was found to accept multiple content-length headers in a request. This could allow attackers to poison a web-cache, bypass web application firewall protection, or conduct cross-site scripting attacks. (CVE-2005-2090)
Tomcat permitted various characters as path delimiters. If Tomcat was used behind certain proxies and configured to only proxy some contexts, an attacker could construct an HTTP request to work around the context restriction and potentially access non-proxied content. (CVE-2007-0450)
Several applications distributed in the JSP examples displayed unfiltered values. If the JSP examples are accessible, these flaws could allow a remote attacker to perform cross-site scripting attacks. (CVE-2006-7195, CVE-2006-7196)
The default Tomcat configuration permitted the use of insecure SSL cipher suites including the anonymous cipher suite. (CVE-2007-1858)
Directory listings were enabled by default in Tomcat. Information stored unprotected under the document root was visible to anyone if the administrator did not disable directory listings. (CVE-2006-3835)
Users should upgrade to these erratum packages which contain Tomcat version 5.5.23 that resolves these issues. Updated jakarta-commons-modeler packages are also included which correct a bug when used with Tomcat 5.5.23.
Solution
Note: /etc/tomcat5/web.xml has been updated to disable directory listing by default. If you have previously modified /etc/tomcat5/web.xml, this change will not be made automatically and you should manually update the value for the "listings" parameter to "false".
Before applying this update, make sure all previously released errata relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory only contains the desired RPMs.
Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate RPMs being upgraded on your system.
Affected Products
| Product | Version | Arch |
|---|---|---|
| Red Hat Application Server v.2 | 2 | x86_64 |
| Red Hat Application Server v.2 | 2 | ppc |
| Red Hat Application Server v.2 | 2 | ia64 |
| Red Hat Application Server v.2 | 2 | i386 |
Updated Packages
- tomcat5-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-jasper-javadoc-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-webapps-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-server-lib-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-jsp-2.0-api-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-common-lib-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-jasper-5.5.23-0jpp_4rh.3.noarch.rpm
- jakarta-commons-modeler-javadoc-2.0-3jpp_2rh.noarch.rpm
- tomcat5-admin-webapps-5.5.23-0jpp_4rh.3.noarch.rpm
- tomcat5-servlet-2.4-api-5.5.23-0jpp_4rh.3.noarch.rpm
Fixes
CVEs
References
- Content from tomcat.apache.org is not included.Content from tomcat.apache.org is not included.http://tomcat.apache.org/security-5.html
- http://www.redhat.com/security/updates/classification/#important
Additional information
- The Red Hat security contact is This content is not included.secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.