Skip to navigation

Security Advisory Important: jbossweb security update

Advisory: RHSA-2012:0074-1
Type: Security Advisory
Severity: Important
Issued on: 2012-01-31
Last updated on: 2012-01-31
Affected Products: JBoss Enterprise Application Platform 5 EL4
JBoss Enterprise Application Platform 5 EL5
JBoss Enterprise Application Platform 5 EL6
CVEs (cve.mitre.org): CVE-2011-1184
CVE-2011-2526
CVE-2011-4610
CVE-2011-4858
CVE-2011-5062
CVE-2011-5063
CVE-2011-5064
CVE-2012-0022

Details

Updated jbossweb packages that fix multiple security issues are now
available for JBoss Enterprise Application 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.

JBoss Web is the web container, based on Apache Tomcat, in JBoss Enterprise
Application Platform. 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
org.apache.tomcat.util.http.Parameters.MAX_COUNT and
org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT system properties in
"jboss-as/server/[PROFILE]/deploy/properties-service.xml". (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
Application Platform's "jboss-as/server/[PROFILE]/deploy/" directory, along
with all other customized configuration files.

Users of JBoss Enterprise Application 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

Updated packages

JBoss Enterprise Application Platform 5 EL4

SRPMS:
jbossweb-2.1.12-3_patch_03.2.ep5.el4.src.rpm
File outdated by:  RHSA-2013:0629
    MD5: f91e6249be57e1496a30ea0e30f30dc7
SHA-256: 8a991a186d3ee13e1522cf097984c0c50535fff6fa0c15310d8f2c960b28f4c7
 
IA-32:
jbossweb-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: df5574e880b464839ac55dc6ca06acf0
SHA-256: 7b864f14fcb23ce0a073087cb1e500c616a5e971ecabaf9b3e6696d43efc340c
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 30d05060761c0d64435e34333fe21be8
SHA-256: c02e7595f0f4b26e3b4d2ce8c1a96429d1fe23d5c23779ba7f179e0f03387c1e
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: ebba23eb9b65e9a6fc681f75d00ac362
SHA-256: 5769a5dd0a4495a856b2fcba24018bda75ffe9ea924596afa1e5979b0fe3a9b9
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: a2f4246055a36cf6943ad08aa84de2bc
SHA-256: 033ec5fbb4257dd1dd197904dbf454af6060d414c3ee2c262ce784ebc7b63a5d
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 41f2e7d1e7927d5cfdbaed2f00d3c539
SHA-256: 7abff0b5e8529146028f2b87b595f4fc4472fd5e9b8e9bc85d63cbb3831e2bd8
 
x86_64:
jbossweb-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: df5574e880b464839ac55dc6ca06acf0
SHA-256: 7b864f14fcb23ce0a073087cb1e500c616a5e971ecabaf9b3e6696d43efc340c
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 30d05060761c0d64435e34333fe21be8
SHA-256: c02e7595f0f4b26e3b4d2ce8c1a96429d1fe23d5c23779ba7f179e0f03387c1e
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: ebba23eb9b65e9a6fc681f75d00ac362
SHA-256: 5769a5dd0a4495a856b2fcba24018bda75ffe9ea924596afa1e5979b0fe3a9b9
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: a2f4246055a36cf6943ad08aa84de2bc
SHA-256: 033ec5fbb4257dd1dd197904dbf454af6060d414c3ee2c262ce784ebc7b63a5d
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el4.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 41f2e7d1e7927d5cfdbaed2f00d3c539
SHA-256: 7abff0b5e8529146028f2b87b595f4fc4472fd5e9b8e9bc85d63cbb3831e2bd8
 
JBoss Enterprise Application Platform 5 EL5

SRPMS:
jbossweb-2.1.12-3_patch_03.2.ep5.el5.src.rpm
File outdated by:  RHSA-2013:0629
    MD5: 172a5371308eb511777174cb64dac4f5
SHA-256: df0e46a253dc62f1164db156421b5f02bc68efe670c51a2edb9a94afa9a1ec2e
 
IA-32:
jbossweb-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 98494bb02d7ad042eea510b062d5fb57
SHA-256: 5b903505bbfe64819523a89dc9d3618965e2bfb52721eac4dc641cde7242e4f7
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 5471036f7ea794391de4c49bdc130b4e
SHA-256: b8874354ee671cdb4eacb842e0a19bcdeb5e51b365fbde25a146fbe79d88593a
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: ae9eeae43ec7a86965d77c7a67fd726e
SHA-256: 5d925158f601181f540dbbc8e1734318b7d52dfe12cb0fadafdfe44c354fc462
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: dd88eaae7b137fc1c9dc6eb575672389
SHA-256: 07022a7c9aa808afc7e941df30b989bde0c31fd072b2b938b522d09d9836756c
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 6ae12c4e34e3770146afcfb627cd02cf
SHA-256: 3223f0c73940b79e4476ba2beb793ede223e82abea9779a75799f64611154b6e
 
x86_64:
jbossweb-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 98494bb02d7ad042eea510b062d5fb57
SHA-256: 5b903505bbfe64819523a89dc9d3618965e2bfb52721eac4dc641cde7242e4f7
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 5471036f7ea794391de4c49bdc130b4e
SHA-256: b8874354ee671cdb4eacb842e0a19bcdeb5e51b365fbde25a146fbe79d88593a
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: ae9eeae43ec7a86965d77c7a67fd726e
SHA-256: 5d925158f601181f540dbbc8e1734318b7d52dfe12cb0fadafdfe44c354fc462
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: dd88eaae7b137fc1c9dc6eb575672389
SHA-256: 07022a7c9aa808afc7e941df30b989bde0c31fd072b2b938b522d09d9836756c
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el5.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 6ae12c4e34e3770146afcfb627cd02cf
SHA-256: 3223f0c73940b79e4476ba2beb793ede223e82abea9779a75799f64611154b6e
 
JBoss Enterprise Application Platform 5 EL6

SRPMS:
jbossweb-2.1.12-3_patch_03.2.ep5.el6.src.rpm
File outdated by:  RHSA-2013:0629
    MD5: 6a2c6359e37de817f7e27feea54a5830
SHA-256: 02837b3ef486c630e1723cc7e8aa48ffe4dfe094c57dec612ce2b72707470408
 
IA-32:
jbossweb-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: dd69a678d1e17336a11971b1ff5ee8be
SHA-256: 7b497fcf857859cf3273b04629753c0b436eac12e2d69ae97368116472a70258
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 21acf1a3e03f2b5c8a3c846783d3dc84
SHA-256: f69b9eaae904040a5e321a480c0a43b8f9acf830230deb1335eb3079c19e974c
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 8bb05f3a1fa76aa0cbe735d1fe3084ed
SHA-256: 45f383f8230b5c560414ddb30a72f364f47d29686a5de015316ca75c5e031a16
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 8ec0f9bde330a93482549c5497ffba74
SHA-256: fe8581b16d2957dfe8c0156ca73c09963c7740165be14fc85ed9b7b725180eb1
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: cbfdade9edb84ed7b99e084beecb6c0e
SHA-256: 2a0a2c6b2b5fc3c28f6a09ea3d9bb3f70667214fc527e46d1e7518b1e61680d4
 
x86_64:
jbossweb-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: dd69a678d1e17336a11971b1ff5ee8be
SHA-256: 7b497fcf857859cf3273b04629753c0b436eac12e2d69ae97368116472a70258
jbossweb-el-1.0-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 21acf1a3e03f2b5c8a3c846783d3dc84
SHA-256: f69b9eaae904040a5e321a480c0a43b8f9acf830230deb1335eb3079c19e974c
jbossweb-jsp-2.1-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 8bb05f3a1fa76aa0cbe735d1fe3084ed
SHA-256: 45f383f8230b5c560414ddb30a72f364f47d29686a5de015316ca75c5e031a16
jbossweb-lib-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: 8ec0f9bde330a93482549c5497ffba74
SHA-256: fe8581b16d2957dfe8c0156ca73c09963c7740165be14fc85ed9b7b725180eb1
jbossweb-servlet-2.5-api-2.1.12-3_patch_03.2.ep5.el6.noarch.rpm
File outdated by:  RHSA-2013:0629
    MD5: cbfdade9edb84ed7b99e084beecb6c0e
SHA-256: 2a0a2c6b2b5fc3c28f6a09ea3d9bb3f70667214fc527e46d1e7518b1e61680d4
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

720948 - CVE-2011-2526 tomcat: security manager restrictions bypass
741401 - CVE-2011-1184 CVE-2011-5062 CVE-2011-5063 CVE-2011-5064 tomcat: Multiple weaknesses in HTTP DIGEST authentication
750521 - CVE-2011-4858 tomcat: hash table collisions CPU usage DoS (oCERT-2011-003)
767871 - CVE-2011-4610 JBoss Web remote denial of service when surrogate pair character is placed at buffer boundary
783359 - CVE-2012-0022 tomcat: large number of parameters DoS


References



These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

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