ResourceBuilderImpl.java in the RichFaces 3.x through 5.x implementation in Red Hat JBoss Web Framework Kit before 2.3.0, Red Hat JBoss Web Platform through 5.2.0, Red Hat JBoss Enterprise Application Platform through 4.3.0 CP10 and 5.x through 5.2.0, Red Hat JBoss BRMS through 5.3.1, Red Hat JBoss SOA Platform through 4.3.0 CP05 and 5.x through 5.3.1, Red Hat JBoss Portal through 4.3 CP07 and 5.x through 5.2.2, and Red Hat JBoss Operations Network through 2.4.2 and 3.x through 3.1.2 does not restrict the classes for which deserialization methods can be called, which allows remote attackers to execute arbitrary code via crafted serialized data.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - ResourceBuilderImpl.java in the RichFaces 3.x through 5.x implementation in Red Hat JBoss Web Framework
    Kit before 2.3.0, Red Hat JBoss Web Platform through 5.2.0, Red Hat JBoss Enterprise Application Platform
    through 4.3.0 CP10 and 5.x through 5.2.0, Red Hat JBoss BRMS through 5.3.1, Red Hat JBoss SOA Platform
    through 4.3.0 CP05 and 5.x through 5.3.1, Red Hat JBoss Portal through 4.3 CP07 and 5.x through 5.2.2, and
    Red Hat JBoss Operations Network through 2.4.2 and 3.x through 3.1.2 does not restrict the classes for
    which deserialization methods can be called, which allows remote attackers to execute arbitrary code via
    crafted serialized data. (CVE-2013-2165)

The remote Redhat Enterprise Linux 5 / 6 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2013:1043 advisory.

    RichFaces 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     Web Platform installation (including all applications and configuration     files).

    All users of Red Hat JBoss Web Platform 5.2.0 on Red Hat Enterprise Linux     4, 5, and 6 are advised to upgrade to these updated packages. The JBoss     server process must be restarted for the update to take effect.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 5 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2013:1044 advisory.

    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.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Updated richfaces packages that fix one security issue are now available for Red Hat JBoss Enterprise Application Platform 5.2.0 for Red Hat Enterprise Linux 4, 5, and 6.

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.

RichFaces 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 5.2.0 on Red Hat Enterprise Linux 4, 5, and 6 are advised to upgrade to these updated packages. The JBoss server process must be restarted for the update to take effect.

ID	Name	Product	Family	Type	Severity
409832	SCA: security update for org.richfaces:richfaces (GHSA-4344-frcp-j22q)	Tenable Cloud Security	SCA Checks	Local	high
409832	SCA: security update for org.richfaces:richfaces (GHSA-4344-frcp-j22q)	Tenable Self-Hosted Container Security	SCA Checks	Local	high
76289	RHEL 5 / 6 : richfaces (RHSA-2013:1043)	Nessus	Red Hat Local Security Checks	Local	high
67240	RHEL 5 : jboss-seam2 (RHSA-2013:1044)	Nessus	Red Hat Local Security Checks	Local	high
67239	RHEL 5 / 6 : richfaces (RHSA-2013:1042)	Nessus	Red Hat Local Security Checks	Local	high

Detections

Analytics

CVE-2013-2165

high

Tenable Plugins

high

high

high

high

high