- Issued:
- 2013-07-10
- Updated:
- 2013-07-10
RHSA-2013:1044 - Security Advisory
Synopsis
Critical: jboss-seam2 security update
Type/Severity
Security Advisory: Critical
Red Hat Insights patch analysis
Identify and remediate systems affected by this advisory.
Topic
Updated jboss-seam2 packages that fix one security issue are now available
for Red Hat JBoss Enterprise Application Platform 4.3.0 CP10 for Red Hat
Enterprise Linux 4 and 5.
The Red Hat Security Response Team has rated this update as having critical
security impact. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available from the CVE link in
the References section.
Description
The JBoss Seam 2 framework is an application framework for building web
applications in Java. The RichFaces component is an open source framework
that adds Ajax capability into existing JavaServer Faces (JSF)
applications.
A flaw was found in the way RichFaces ResourceBuilderImpl handled
deserialization. A remote attacker could use this flaw to trigger the
execution of the deserialization methods in any serializable class deployed
on the server. This could lead to a variety of security impacts depending
on the deserialization logic of these classes. (CVE-2013-2165)
The fix for this issue introduces a whitelist to limit classes that can be
deserialized by RichFaces.
If you require to whitelist a class that is not already listed, for
example, a custom class, you can achieve this by following one of these
methods:
Method 1: Implementing the SerializableResource interface.
In RichFaces 3, this is defined at
org.ajax4jsf.resource.SerializableResource and in RichFaces 4/5, at
org.richfaces.resource.SerializableResource.
Method 2: Adding the class to the resource-serialization.properties file
(a default properties file is provided once this update is applied).
To do this you can extend the framework provided properties file that is
available under org.ajax4jsf.resource in RichFaces 3 and
org.richfaces.resource in RichFaces 4/5. The modified properties file has
to be copied into the classpath of your deployment under the
version-specific packages.
Where possible, it is recommended that Method 1 be followed.
Red Hat would like to thank Takeshi Terada (Mitsui Bussan Secure
Directions, Inc.) for reporting this issue.
Warning: Before applying this update, back up your existing Red Hat JBoss
Enterprise Application Platform installation (including all applications
and configuration files).
All users of Red Hat JBoss Enterprise Application Platform 4.3.0 CP10 on
Red Hat Enterprise Linux 4 and 5 are advised to upgrade to these updated
packages. The JBoss 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.
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 Application Platform 4.3.0 x86_64
- JBoss Enterprise Application Platform 4.3.0 i386
Fixes
- BZ - 973570 - CVE-2013-2165 JBoss RichFaces: Remote code execution due to insecure deserialization
CVEs
JBoss Enterprise Application Platform 4.3.0
SRPM | |
---|---|
jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el5.src.rpm | SHA-256: 9126a1bab20bc506f417107f47c5a3cbf41b9a59af3bbb501a6185eaa87a61f1 |
x86_64 | |
jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el5.noarch.rpm | SHA-256: 184f3e7bb39672b444d73f3fe6fad667d471090b0e5928fde4ea0f9d39c6e2a1 |
jboss-seam2-docs-2.0.2.FP_SEC1-1.ep2.6.el5.noarch.rpm | SHA-256: 25c72936e9b8181f3307222f766f50654507bb1f6a6af7ddbe363a06bc487123 |
i386 | |
jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el5.noarch.rpm | SHA-256: 184f3e7bb39672b444d73f3fe6fad667d471090b0e5928fde4ea0f9d39c6e2a1 |
jboss-seam2-docs-2.0.2.FP_SEC1-1.ep2.6.el5.noarch.rpm | SHA-256: 25c72936e9b8181f3307222f766f50654507bb1f6a6af7ddbe363a06bc487123 |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.