Issued:
2014-07-03
Updated:
2014-07-03

RHSA-2014:0834 - Security Advisory

Synopsis

Moderate: Red Hat JBoss Web Server 2.0.1 tomcat6 security and bug fix update

Type/Severity

Security Advisory: Moderate

Topic

Updated tomcat6 packages that fix three security issues and one bug are now
available for Red Hat JBoss Web Server 2.0.1 on Red Hat Enterprise Linux 5
and 6.

The Red Hat Security Response Team has rated this update as having Moderate
security impact. Common Vulnerability Scoring System (CVSS) base scores,
which give detailed severity ratings, are available for each vulnerability
from the CVE links in the References section.

Description

Red Hat JBoss Web Server is a fully integrated and certified set of
components for hosting Java web applications. It is comprised of the Apache
HTTP Server, the Apache Tomcat Servlet container, Apache Tomcat Connector
(mod_jk), JBoss HTTP Connector (mod_cluster), Hibernate, and the Tomcat
Native library.

It was discovered that Apache Tomcat did not limit the length of chunk
sizes when using chunked transfer encoding. A remote attacker could use
this flaw to perform a denial of service attack against Tomcat by streaming
an unlimited quantity of data, leading to excessive consumption of server
resources. (CVE-2014-0075)

It was found that Apache Tomcat did not check for overflowing values when
parsing request content length headers. A remote attacker could use this
flaw to perform an HTTP request smuggling attack on a Tomcat server located
behind a reverse proxy that processed the content length header correctly.
(CVE-2014-0099)

It was found that the org.apache.catalina.servlets.DefaultServlet
implementation in Apache Tomcat allowed the definition of XML External
Entities (XXEs) in provided XSLTs. A malicious application could use this
to circumvent intended security restrictions to disclose sensitive
information. (CVE-2014-0096)

The CVE-2014-0075 issue was discovered by David Jorm of Red Hat Product
Security.

This update also fixes the following bug:

The tomcat6-lib-6.0.37-19_patch_04.ep6.el5 package, provided as a
dependency of Red Hat JBoss Web Server 2.0.1, included a build of
commons-dbcp.jar that used an incorrect java package name, causing
applications using this dependency to not function properly. With this
update, the java package name has been corrected. (BZ#1101287)

All users of Red Hat JBoss Web Server 2.0.1 are advised to upgrade to these
updated tomcat6 packages, which contain backported patches to correct these
issues. The Red Hat JBoss Web Server process must be restarted for the
update to take effect.

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied, and back up your existing Red
Hat JBoss Web Server installation (including all applications and
configuration files).

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/knowledge/articles/11258

Affected Products

  • JBoss Enterprise Web Server 2 for RHEL 6 x86_64
  • JBoss Enterprise Web Server 2 for RHEL 6 i386
  • JBoss Enterprise Web Server 2 for RHEL 5 x86_64
  • JBoss Enterprise Web Server 2 for RHEL 5 i386

Fixes

  • BZ - 1072776 - CVE-2014-0075 Tomcat/JBossWeb: Limited DoS in chunked transfer encoding input filter
  • BZ - 1088342 - CVE-2014-0096 Tomcat/JBossWeb: XXE vulnerability via user supplied XSLTs
  • BZ - 1102030 - CVE-2014-0099 Tomcat/JBossWeb: Request smuggling via malicious content length header

CVEs

References

JBoss Enterprise Web Server 2 for RHEL 6

SRPM
tomcat6-6.0.37-29_patch_05.ep6.el6.src.rpm SHA-256: 7fbb86033438a88df61d1840d7da66b9ca4b53ed24e00998a48567caf92f619a
x86_64
tomcat6-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: acb0a6e313b9cffb60417ea32db8e5b3da3f9a667fbd95441f6e2fe473af7f32
tomcat6-admin-webapps-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 5f40ba9532b2f2d094ae667f40441238674296c31968856414f3cac5c0eceeda
tomcat6-docs-webapp-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 3f7faf6bb9d41c67cd7e3d48f27cbe8fabba91488256c6eecea40f539a3a998c
tomcat6-el-2.1-api-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 6eefab68a3e3fdb801b0859ab97866995f4bd96d6f9a49ee71bfbeeb531a37e2
tomcat6-javadoc-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: ef4421172971cc5576bdf04ad71e9854d59f2cb4d56a7c3fd0dc3e62801650e7
tomcat6-jsp-2.1-api-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 4de110cc4261f2c657003920c72facc337d9dcdd77a3943490347226c31896a2
tomcat6-lib-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 86c0e08295d08262a7e675c03c7acd58bd18ab59be3389949cc5b5239dc2c0e4
tomcat6-log4j-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 219b6dbfcceb893926693bf944513b3e90fed13e984443e1bffee60689cc352b
tomcat6-servlet-2.5-api-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 40f7938d1a6a8df447a2b440f50955147367e098a8459c1f115934b9125bbf27
tomcat6-webapps-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 8cac0b993024ddb617b6b8385aee04460b4adc6748579f94a802b67e3a02970d
i386
tomcat6-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: acb0a6e313b9cffb60417ea32db8e5b3da3f9a667fbd95441f6e2fe473af7f32
tomcat6-admin-webapps-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 5f40ba9532b2f2d094ae667f40441238674296c31968856414f3cac5c0eceeda
tomcat6-docs-webapp-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 3f7faf6bb9d41c67cd7e3d48f27cbe8fabba91488256c6eecea40f539a3a998c
tomcat6-el-2.1-api-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 6eefab68a3e3fdb801b0859ab97866995f4bd96d6f9a49ee71bfbeeb531a37e2
tomcat6-javadoc-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: ef4421172971cc5576bdf04ad71e9854d59f2cb4d56a7c3fd0dc3e62801650e7
tomcat6-jsp-2.1-api-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 4de110cc4261f2c657003920c72facc337d9dcdd77a3943490347226c31896a2
tomcat6-lib-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 86c0e08295d08262a7e675c03c7acd58bd18ab59be3389949cc5b5239dc2c0e4
tomcat6-log4j-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 219b6dbfcceb893926693bf944513b3e90fed13e984443e1bffee60689cc352b
tomcat6-servlet-2.5-api-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 40f7938d1a6a8df447a2b440f50955147367e098a8459c1f115934b9125bbf27
tomcat6-webapps-6.0.37-29_patch_05.ep6.el6.noarch.rpm SHA-256: 8cac0b993024ddb617b6b8385aee04460b4adc6748579f94a802b67e3a02970d

JBoss Enterprise Web Server 2 for RHEL 5

SRPM
tomcat6-6.0.37-20_patch_04.ep6.el5.src.rpm SHA-256: df018b51802845f5eca2de85df3dc42e5c955d180fe6fec888c303a036f3cb3d
x86_64
tomcat6-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 3565f50b52b5e1e5c056d5a56a0829e89fd4adf41e6beb3fffabca8f9a183e0e
tomcat6-admin-webapps-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 1af3153db93d6a8b14c48aae43ef73104b206551deae1c4057603f967d423843
tomcat6-docs-webapp-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 28e2dad35e9a04cf56b9be187b3d626cdf2a02c584bc5ca13e7a9a4dee708011
tomcat6-el-2.1-api-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 1405a3f79a4e459ee3fa20256e70cbad89b1d11eaedbc36147260b31650d8b1c
tomcat6-javadoc-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 91933ca3c0d34bb9dcdd38b8961cd324434b07d374dec2e40b6e848b977ea835
tomcat6-jsp-2.1-api-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 317e25953e3fcad20779ca356d83beed92454065e75d8dfff73298c8650df7ec
tomcat6-lib-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 58e6fc09f9b362b845bba18ca994d5a713d8427a82fbef47e0ccd2395009c9f7
tomcat6-log4j-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 63c3a930bd0bd366e0f938408f8a1eeab258465eeba6761d7864c65a0b8e1c9b
tomcat6-servlet-2.5-api-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 98375256b028e5bd630272ebc523481fc69dc9f503ce00ce0e193fb473b29885
tomcat6-webapps-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: a37c13b1b28c7e4d91f38ac1156e6d8805ae8e3866f699c06015c2b54184181a
i386
tomcat6-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 3565f50b52b5e1e5c056d5a56a0829e89fd4adf41e6beb3fffabca8f9a183e0e
tomcat6-admin-webapps-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 1af3153db93d6a8b14c48aae43ef73104b206551deae1c4057603f967d423843
tomcat6-docs-webapp-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 28e2dad35e9a04cf56b9be187b3d626cdf2a02c584bc5ca13e7a9a4dee708011
tomcat6-el-2.1-api-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 1405a3f79a4e459ee3fa20256e70cbad89b1d11eaedbc36147260b31650d8b1c
tomcat6-javadoc-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 91933ca3c0d34bb9dcdd38b8961cd324434b07d374dec2e40b6e848b977ea835
tomcat6-jsp-2.1-api-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 317e25953e3fcad20779ca356d83beed92454065e75d8dfff73298c8650df7ec
tomcat6-lib-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 58e6fc09f9b362b845bba18ca994d5a713d8427a82fbef47e0ccd2395009c9f7
tomcat6-log4j-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 63c3a930bd0bd366e0f938408f8a1eeab258465eeba6761d7864c65a0b8e1c9b
tomcat6-servlet-2.5-api-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: 98375256b028e5bd630272ebc523481fc69dc9f503ce00ce0e193fb473b29885
tomcat6-webapps-6.0.37-20_patch_04.ep6.el5.noarch.rpm SHA-256: a37c13b1b28c7e4d91f38ac1156e6d8805ae8e3866f699c06015c2b54184181a

The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.