Bug 1027052 (CVE-2013-4521)

Summary: CVE-2013-4521 Nuxeo RichFaces: Remote code execution due to insecure deserialization
Product: [Other] Security Response Reporter: David Jorm <djorm>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED NOTABUG QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: unspecifiedCC: mjc, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
A flaw was found in Nuxeo RichFaces where it improperly deserialized data. An attacker could use this flaw to obtain execution on deserialization methods on serializable classes deployed on the server. This can possibly lead to unauthenticated remote code execution.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-14 00:42:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Jorm 2013-11-06 02:04:31 UTC
A flaw was found in the way Nuxeo RichFaces 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. On Nuxeo Server 5.6, 5.7.4 and 5.8, this can be used to trigger deserialization logic which leads to unauthenticated remote code execution.

Comment 1 David Jorm 2013-11-06 02:06:29 UTC
Statement:

Not vulnerable. This flaw does not affect RichFaces as shipped with various JBoss products. These products use JBoss RichFaces, which is covered by CVE-2013-2165. This flaw pertains specifically to Nuxeo RichFaces.

Comment 2 David Jorm 2013-11-08 00:16:12 UTC
Upstream patch commit:

https://github.com/nuxeo/richfaces/commit/6cbad2a6dcb70d3e33a6ce5879b1a3ad79eb1aec

Comment 3 Murray McAllister 2013-11-08 00:23:17 UTC
Acknowledgements:

This issue was discovered by Arun Neelicattu and David Jorm of the Red Hat Security Response Team.