Synopsis

Important: tomcat5 security update

Type/Severity

Security Advisory: Important

Topic

Updated tomcat5 packages that fix several security issues are now available
for JBoss Enterprise Web Server 1.0.0 for Red Hat Enterprise Linux 4 and 5.

This update has been rated as having important security impact by the Red
Hat Security Response Team.

[Updated 23 September 2009]
This erratum has been updated to include replacement packages for JBoss
Enterprise Web Server 1.0.0 for Red Hat Enterprise Linux 4. The original
packages did not contain a fix for the low security impact issue
CVE-2009-0783. The packages for JBoss Enterprise Web Server 1.0.0 for Red
Hat Enterprise Linux 5 are unchanged as they included the fix for
CVE-2009-0783.

Description

Apache Tomcat is a servlet container for the Java Servlet and JavaServer
Pages (JSP) technologies.

It was discovered that Tomcat does not properly handle a certain character
and character sequence in cookie values. A remote attacker could use this
flaw to obtain sensitive information, such as session IDs, and then use
this information for session hijacking attacks. (CVE-2007-5333)

Note: The fix for the CVE-2007-5333 flaw changes the default cookie
processing behavior: With this update, version 0 cookies that contain
values that must be quoted to be valid are automatically changed to version
1 cookies. To reactivate the previous, but insecure behavior, add the
following entry to the "/etc/tomcat5/catalina.properties" file:

org.apache.tomcat.util.http.ServerCookie.VERSION_SWITCH=false

It was discovered that request dispatchers did not properly normalize user
requests that have trailing query strings, allowing remote attackers to
send specially-crafted requests that would cause an information leak.
(CVE-2008-5515)

A flaw was found in the way the Tomcat AJP (Apache JServ Protocol)
connector processes AJP connections. An attacker could use this flaw to
send specially-crafted requests that would cause a temporary denial of
service. (CVE-2009-0033)

It was discovered that the error checking methods of certain authentication
classes did not have sufficient error checking, allowing remote attackers
to enumerate (via brute force methods) usernames registered with
applications running on Tomcat when FORM-based authentication was used.
(CVE-2009-0580)

It was discovered that web applications containing their own XML parsers
could replace the XML parser Tomcat uses to parse configuration files. A
malicious web application running on a Tomcat instance could read or,
potentially, modify the configuration and XML-based data of other web
applications deployed on the same Tomcat instance. (CVE-2009-0783)

Users of Tomcat should upgrade to these updated packages, which contain
backported patches to resolve these issues. Tomcat must be restarted for
this update to take effect.

Solution

Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.

This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
http://kbase.redhat.com/faq/docs/DOC-11259

Affected Products

• JBoss Enterprise Web Server 1 for RHEL 5 x86_64
• JBoss Enterprise Web Server 1 for RHEL 5 i386

Fixes

• BZ - 427766 - CVE-2007-5333 Improve cookie parsing for tomcat5
• BZ - 493381 - CVE-2009-0033 tomcat6 Denial-Of-Service with AJP connection
• BZ - 503978 - CVE-2009-0580 tomcat6 Information disclosure in authentication classes
• BZ - 504153 - CVE-2009-0783 tomcat XML parser information disclosure
• BZ - 504753 - CVE-2008-5515 tomcat request dispatcher information disclosure vulnerability

CVEs

• CVE-2008-5515
• CVE-2009-0783
• CVE-2009-0580
• CVE-2009-0033
• CVE-2007-5333

References

• http://tomcat.apache.org/security-5.html
• http://www.redhat.com/security/updates/classification/#important

JBoss Enterprise Web Server 1 for RHEL 5

SRPM
tomcat5-5.5.23-0jpp.9.6.ep5.el5.src.rpm	SHA-256: 3dada80320b638f63fa4fcf569a9705c59f7edb5687358f7a39a60dd2bfc494a
x86_64
tomcat5-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: f758568af4956afe477aed94ff0ca0f70f7ec14261f8b0638749dcf46012f59b
tomcat5-admin-webapps-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: fd584fe2ccddba9238554826747ac9406ee06ad462b9282362a8747ba9a6d85e
tomcat5-common-lib-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 6fc293a3c79e1ee0a392b88fb7089ed573a1f9c695ca6005d4072ea9a3848367
tomcat5-jasper-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: da7a1c08ddbe71afad13198b71f2ae0eb7b8ad511a67dec0a01c5370f2d0b913
tomcat5-jasper-javadoc-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 1212abf56d4bc5c1fd6f406b868bb281bb0b6761c284b3ab10d1053cf705e1f4
tomcat5-jsp-2.0-api-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 3dc4ddbc8b680c2c5853c41ed25051c5fc38a8163da3fdf6614774afcc44b682
tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: fd43caf74d4ab2dbdfaabb844509e01f59618a82d9e74e768568a63a801160fa
tomcat5-server-lib-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: bf9558dc813fdac3c2e988a1d0532c2c03c3d1898ef186c14c0387fcc3584aeb
tomcat5-servlet-2.4-api-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 0c98389379f30c92c64a146a8caf18a17f2358b86a8c44fed46d00f618f67644
tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: c0f7d08390c9de070207a5fa088d000ee7cb02289cab863ded7d5dd5da22d3f1
tomcat5-webapps-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 95c4e1d7174c9d1de9e1fd3adaadaea60876c7faaec872c972f03c6b718bba1a
i386
tomcat5-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: f758568af4956afe477aed94ff0ca0f70f7ec14261f8b0638749dcf46012f59b
tomcat5-admin-webapps-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: fd584fe2ccddba9238554826747ac9406ee06ad462b9282362a8747ba9a6d85e
tomcat5-common-lib-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 6fc293a3c79e1ee0a392b88fb7089ed573a1f9c695ca6005d4072ea9a3848367
tomcat5-jasper-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: da7a1c08ddbe71afad13198b71f2ae0eb7b8ad511a67dec0a01c5370f2d0b913
tomcat5-jasper-javadoc-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 1212abf56d4bc5c1fd6f406b868bb281bb0b6761c284b3ab10d1053cf705e1f4
tomcat5-jsp-2.0-api-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 3dc4ddbc8b680c2c5853c41ed25051c5fc38a8163da3fdf6614774afcc44b682
tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: fd43caf74d4ab2dbdfaabb844509e01f59618a82d9e74e768568a63a801160fa
tomcat5-server-lib-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: bf9558dc813fdac3c2e988a1d0532c2c03c3d1898ef186c14c0387fcc3584aeb
tomcat5-servlet-2.4-api-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 0c98389379f30c92c64a146a8caf18a17f2358b86a8c44fed46d00f618f67644
tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: c0f7d08390c9de070207a5fa088d000ee7cb02289cab863ded7d5dd5da22d3f1
tomcat5-webapps-5.5.23-0jpp.9.6.ep5.el5.noarch.rpm	SHA-256: 95c4e1d7174c9d1de9e1fd3adaadaea60876c7faaec872c972f03c6b718bba1a