[ https://issues.apache.org/jira/browse/COLLECTIONS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011116#comment-15011116 ]
Tiago Stürmer Daitx commented on COLLECTIONS-580: ------------------------------------------------- According to CVE assignment team [1] no CVE ID will be allocated for this issue and: "The CVE-2015-4852 ID came from Oracle and must remain associated only with Oracle's own software (WebLogic Server is the product they've named)." but then Oracle's Thomas Keefe reply [1] to that thread stated: "We do not have a problem with this use of the CVE# we registered (CVE-2015-4852)." [1] http://www.openwall.com/lists/oss-security/2015/11/17/19 [2] http://www.openwall.com/lists/oss-security/2015/11/18/1 > Arbitrary remote code execution with InvokerTransformer > ------------------------------------------------------- > > Key: COLLECTIONS-580 > URL: https://issues.apache.org/jira/browse/COLLECTIONS-580 > Project: Commons Collections > Issue Type: Bug > Affects Versions: 3.0, 4.0 > Reporter: Philippe Marschall > Fix For: 3.2.2, 4.1 > > Attachments: COLLECTIONS-580.patch > > > With {{InvokerTransformer}} serializable collections can be build that > execute arbitrary Java code. > {{sun.reflect.annotation.AnnotationInvocationHandler#readObject}} invokes > {{#entrySet}} and {{#get}} on a deserialized collection. If you have an > endpoint that accepts serialized Java objects (JMX, RMI, remote EJB, ...) you > can combine the two to create arbitrary remote code execution vulnerability. > I don't know of a good fix short of removing {{InvokerTransformer}} or making > it not Serializable. Both probably break existing applications. > This is not my research, but has been discovered by other people. > https://github.com/frohoff/ysoserial > http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)