- Issued:
- 2012-01-31
- Updated:
- 2012-01-31
RHSA-2012:0076 - Security Advisory
Synopsis
Important: jbossweb security update
Type/Severity
Security Advisory: Important
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated jbossweb packages that fix multiple security issues are now
available for JBoss Enterprise Web Platform 5.1.2 for Red Hat Enterprise
Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having
important 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
JBoss Web is a web container based on Apache Tomcat. It provides a single
deployment platform for the JavaServer Pages (JSP) and Java Servlet
technologies.
A flaw was found in the way JBoss Web handled UTF-8 surrogate pair
characters. If JBoss Web was hosting an application with UTF-8 character
encoding enabled, or that included user-supplied UTF-8 strings in a
response, a remote attacker could use this flaw to cause a denial of
service (infinite loop) on the JBoss Web server. (CVE-2011-4610)
It was found that the Java hashCode() method implementation was susceptible
to predictable hash collisions. A remote attacker could use this flaw to
cause JBoss Web to use an excessive amount of CPU time by sending an HTTP
request with a large number of parameters whose names map to the same hash
value. This update introduces a limit on the number of parameters and
headers processed per request to mitigate this issue. The default limit is
512 for parameters and 128 for headers. These defaults can be changed by
setting the "-Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=x" and
"-Dorg.apache.tomcat.util.http.MimeHeaders.MAX_COUNT=x" system properties
as JAVA_OPTS entries in "jboss-as-web/bin/run.conf". (CVE-2011-4858)
It was found that JBoss Web did not handle large numbers of parameters and
large parameter values efficiently. A remote attacker could make a JBoss
Web server use an excessive amount of CPU time by sending an HTTP request
containing a large number of parameters or large parameter values. This
update introduces limits on the number of parameters and headers processed
per request to address this issue. Refer to the CVE-2011-4858 description
for information about the org.apache.tomcat.util.http.Parameters.MAX_COUNT
and org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT system properties.
(CVE-2012-0022)
Multiple flaws were found in the way JBoss Web handled HTTP DIGEST
authentication. These flaws weakened the JBoss Web HTTP DIGEST
authentication implementation, subjecting it to some of the weaknesses of
HTTP BASIC authentication, for example, allowing remote attackers to
perform session replay attacks. (CVE-2011-1184, CVE-2011-5062,
CVE-2011-5063, CVE-2011-5064)
A flaw was found in the way JBoss Web handled sendfile request attributes
when using the HTTP APR (Apache Portable Runtime) or NIO (Non-Blocking I/O)
connector. A malicious web application running on a JBoss Web instance
could use this flaw to bypass security manager restrictions and gain access
to files it would otherwise be unable to access, or possibly terminate the
Java Virtual Machine (JVM). (CVE-2011-2526)
Red Hat would like to thank NTT OSSC for reporting CVE-2011-4610; oCERT for
reporting CVE-2011-4858; and the Apache Tomcat project for reporting
CVE-2011-2526. oCERT acknowledges Julian Wälde and Alexander Klink as the
original reporters of CVE-2011-4858.
Warning: Before applying this update, back up your JBoss Enterprise Web
Platform's "jboss-as-web/server/[PROFILE]/deploy/" directory and any other
customized configuration files.
Users of JBoss Enterprise Web Platform 5.1.2 on Red Hat Enterprise Linux 4,
5, and 6 should upgrade to these updated packages, which correct these
issues. The JBoss server process must be restarted for this update to take
effect.
Solution
Before applying this update, make sure all previously-released errata
relevant to your system have been applied.
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/kb/docs/DOC-11259
Affected Products
- JBoss Enterprise Web Platform 5 for RHEL 6 x86_64
- JBoss Enterprise Web Platform 5 for RHEL 6 i386
- JBoss Enterprise Web Platform 5 for RHEL 5 x86_64
- JBoss Enterprise Web Platform 5 for RHEL 5 i386
Fixes
- BZ - 720948 - CVE-2011-2526 tomcat: security manager restrictions bypass
- BZ - 741401 - CVE-2011-1184 CVE-2011-5062 CVE-2011-5063 CVE-2011-5064 tomcat: Multiple weaknesses in HTTP DIGEST authentication
- BZ - 750521 - CVE-2011-4858 tomcat: hash table collisions CPU usage DoS (oCERT-2011-003)
- BZ - 767871 - CVE-2011-4610 JBoss Web remote denial of service when surrogate pair character is placed at buffer boundary
- BZ - 783359 - CVE-2012-0022 tomcat: large number of parameters DoS
CVEs
JBoss Enterprise Web Platform 5 for RHEL 6
SRPM | |
---|---|
jbossweb-2.1.12-3_patch_03.2.ep5.el6.src.rpm | SHA-256: 02837b3ef486c630e1723cc7e8aa48ffe4dfe094c57dec612ce2b72707470408 |
x86_64 | |
jbossweb-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: 7b497fcf857859cf3273b04629753c0b436eac12e2d69ae97368116472a70258 |
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: f69b9eaae904040a5e321a480c0a43b8f9acf830230deb1335eb3079c19e974c |
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: 45f383f8230b5c560414ddb30a72f364f47d29686a5de015316ca75c5e031a16 |
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: fe8581b16d2957dfe8c0156ca73c09963c7740165be14fc85ed9b7b725180eb1 |
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: 2a0a2c6b2b5fc3c28f6a09ea3d9bb3f70667214fc527e46d1e7518b1e61680d4 |
i386 | |
jbossweb-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: 7b497fcf857859cf3273b04629753c0b436eac12e2d69ae97368116472a70258 |
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: f69b9eaae904040a5e321a480c0a43b8f9acf830230deb1335eb3079c19e974c |
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: 45f383f8230b5c560414ddb30a72f364f47d29686a5de015316ca75c5e031a16 |
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: fe8581b16d2957dfe8c0156ca73c09963c7740165be14fc85ed9b7b725180eb1 |
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm | SHA-256: 2a0a2c6b2b5fc3c28f6a09ea3d9bb3f70667214fc527e46d1e7518b1e61680d4 |
JBoss Enterprise Web Platform 5 for RHEL 5
SRPM | |
---|---|
jbossweb-2.1.12-3_patch_03.2.ep5.el5.src.rpm | SHA-256: df0e46a253dc62f1164db156421b5f02bc68efe670c51a2edb9a94afa9a1ec2e |
x86_64 | |
jbossweb-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 5b903505bbfe64819523a89dc9d3618965e2bfb52721eac4dc641cde7242e4f7 |
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: b8874354ee671cdb4eacb842e0a19bcdeb5e51b365fbde25a146fbe79d88593a |
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 5d925158f601181f540dbbc8e1734318b7d52dfe12cb0fadafdfe44c354fc462 |
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 07022a7c9aa808afc7e941df30b989bde0c31fd072b2b938b522d09d9836756c |
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 3223f0c73940b79e4476ba2beb793ede223e82abea9779a75799f64611154b6e |
i386 | |
jbossweb-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 5b903505bbfe64819523a89dc9d3618965e2bfb52721eac4dc641cde7242e4f7 |
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: b8874354ee671cdb4eacb842e0a19bcdeb5e51b365fbde25a146fbe79d88593a |
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 5d925158f601181f540dbbc8e1734318b7d52dfe12cb0fadafdfe44c354fc462 |
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 07022a7c9aa808afc7e941df30b989bde0c31fd072b2b938b522d09d9836756c |
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm | SHA-256: 3223f0c73940b79e4476ba2beb793ede223e82abea9779a75799f64611154b6e |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.