RHSA-2012:0075: Important: jbossweb security update

Published Jan 31, 2012
·
Updated

JBoss Web is the web container, based on Apache Tomcat, in JBoss EnterpriseApplication Platform. It provides a single deployment platform for theJavaServer Pages (JSP) and Java Servlet technologies.A flaw was found in the way JBoss Web handled UTF-8 surrogate paircharacters. If JBoss Web was hosting an application with UTF-8 characterencoding enabled, or that included user-supplied UTF-8 strings in aresponse, a remote attacker could use this flaw to cause a denial ofservice (infinite loop) on the JBoss Web server. (CVE-2011-4610)It was found that the Java hashCode() method implementation wassusceptible to predictable hash collisions. A remote attacker could usethis flaw to cause JBoss Web to use an excessive amount of CPU time bysending an HTTP request with a large number of parameters whose names mapto the same hash value. This update introduces a limit on the number ofparameters and headers processed per request to mitigate this issue. Thedefault limit is 512 for parameters and 128 for headers. These defaultscan be changed by setting theorg.apache.tomcat.util.http.Parameters.MAXCOUNT andorg.apache.tomcat.util.http.MimeHeaders.MAXCOUNT 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 andlarge parameter values efficiently. A remote attacker could make a JBossWeb server use an excessive amount of CPU time by sending an HTTP requestcontaining a large number of parameters or large parameter values. Thisupdate introduces limits on the number of parameters and headers processedper request to address this issue. Refer to the CVE-2011-4858 descriptionfor information about the org.apache.tomcat.util.http.Parameters.MAXCOUNTand org.apache.tomcat.util.http.MimeHeaders.MAXCOUNT system properties.(CVE-2012-0022)Multiple flaws were found in the way JBoss Web handled HTTP DIGESTauthentication. These flaws weakened the JBoss Web HTTP DIGESTauthentication implementation, subjecting it to some of the weaknesses ofHTTP BASIC authentication, for example, allowing remote attackers toperform 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 attributeswhen using the HTTP APR (Apache Portable Runtime) or NIO (Non-Blocking I/O)connector. A malicious web application running on a JBoss Web instancecould use this flaw to bypass security manager restrictions and gain accessto files it would otherwise be unable to access, or possibly terminate theJava Virtual Machine (JVM). (CVE-2011-2526)Red Hat would like to thank NTT OSSC for reporting CVE-2011-4610; oCERT forreporting CVE-2011-4858; and the Apache Tomcat project for reportingCVE-2011-2526. oCERT acknowledges Julian Wälde and Alexander Klink as theoriginal reporters of CVE-2011-4858.Warning: Before applying this update, back up your JBoss EnterpriseApplication Platform's "jboss-as/server/[PROFILE]/deploy/" directory, alongwith all other customized configuration files.All users of JBoss Enterprise Application Platform 5.1.2 as provided fromthe Red Hat Customer Portal are advised to install this update.

Affected Software

1 affected component
JBoss JBoss Web

Remediation

Event History

Jan 31, 2012
Advisory Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionAffected Software

Frequently Asked Questions

1

What is the severity of RHSA-2012:0075?

The severity of RHSA-2012:0075 is classified as moderate.

2

How do I fix RHSA-2012:0075?

To fix RHSA-2012:0075, you should update JBoss Web to the latest version provided in the advisory.

3

What vulnerabilities are addressed in RHSA-2012:0075?

RHSA-2012:0075 addresses a flaw in the way JBoss Web handles UTF-8 surrogate pair characters.

4

Which software versions are affected by RHSA-2012:0075?

RHSA-2012:0075 affects JBoss Web versions prior to the patched release.

5

Is there a workaround for RHSA-2012:0075?

There is no specific workaround for RHSA-2012:0075 other than applying the recommended updates.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203