Red Hat Security Advisory 2013-1044-01 - 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 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.
d18a74069a96a4aaa1652df273b226c9ec81f840a9d532e9124b8e2d2d808e2a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=====================================================================
Red Hat Security Advisory
Synopsis: Critical: jboss-seam2 security update
Advisory ID: RHSA-2013:1044-01
Product: Red Hat JBoss Enterprise Application Platform
Advisory URL: https://rhn.redhat.com/errata/RHSA-2013-1044.html
Issue date: 2013-07-10
CVE Names: CVE-2013-2165
=====================================================================
1. Summary:
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.
2. Relevant releases/architectures:
Red Hat JBoss Enterprise Application Platform 4.3.0 for RHEL 4 AS - noarch
Red Hat JBoss Enterprise Application Platform 4.3.0 for RHEL 4 ES - noarch
Red Hat JBoss Enterprise Application Platform 4.3.0 for RHEL 5 Server - noarch
3. 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.
4. 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
5. Bugs fixed (https://bugzilla.redhat.com/):
973570 - CVE-2013-2165 JBoss RichFaces: Remote code execution due to insecure deserialization
6. Package List:
Red Hat JBoss Enterprise Application Platform 4.3.0 for RHEL 4 AS:
Source:
ftp://updates.redhat.com/enterprise/4AS/en/JBEAP/SRPMS/jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el4.src.rpm
noarch:
jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el4.noarch.rpm
jboss-seam2-docs-2.0.2.FP_SEC1-1.ep2.6.el4.noarch.rpm
Red Hat JBoss Enterprise Application Platform 4.3.0 for RHEL 4 ES:
Source:
ftp://updates.redhat.com/enterprise/4ES/en/JBEAP/SRPMS/jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el4.src.rpm
noarch:
jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el4.noarch.rpm
jboss-seam2-docs-2.0.2.FP_SEC1-1.ep2.6.el4.noarch.rpm
Red Hat JBoss Enterprise Application Platform 4.3.0 for RHEL 5 Server:
Source:
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/JBEAP/SRPMS/jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el5.src.rpm
noarch:
jboss-seam2-2.0.2.FP_SEC1-1.ep2.6.el5.noarch.rpm
jboss-seam2-docs-2.0.2.FP_SEC1-1.ep2.6.el5.noarch.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://access.redhat.com/security/team/key/#package
7. References:
https://www.redhat.com/security/data/cve/CVE-2013-2165.html
https://access.redhat.com/security/updates/classification/#critical
8. Contact:
The Red Hat security contact is <secalert@redhat.com>. More contact
details at https://access.redhat.com/security/team/contact/
Copyright 2013 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
iD8DBQFR3g6+XlSAg2UNWIIRAnz/AKCPsV4ZBdrec2jbsJlrTobo8/GncwCcCch6
lmfIU45PMKM64d80vmz9h9g=
=B9ld
-----END PGP SIGNATURE-----
--
RHSA-announce mailing list
RHSA-announce@redhat.com
https://www.redhat.com/mailman/listinfo/rhsa-announce