oss-security - [CVE-2015-3253] Apache Groovy Zero-Day Vulnerability Disclosure

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CADQzvmmYC7RbZnsQ8O63XN4HCMYh9RGRdMiuWupVt=u=pjH8+g@mail.gmail.com>
Date: Thu, 16 Jul 2015 12:02:21 +0200
From: Cédric Champeau <cchampeau@...che.org>
To: users@...ovy.incubator.apache.org, dev@...ovy.incubator.apache.org
Cc: security@...che.org, oss-security@...ts.openwall.com, 
	bugtraq@...urityfocus.com
Subject: [CVE-2015-3253] Apache Groovy Zero-Day Vulnerability Disclosure

*Severity*: Important

*Vendor*: The Apache Software Foundation
*Versions Affected*:

All unsupported versions ranging from 1.7.0 to 2.4.3.

*Impact*

Remote execution of untrusted code, DoS

*Description*

When an application has Groovy on classpath and that it uses standard Java
serialization mechanims to communicate between servers, or to store local
data, it is possible for an attacker to bake a special serialized object
that will execute code directly when deserialized. All applications which
rely on serialization and do not isolate the code which deserializes
objects are subject to this vulnerability.

*Mitigation*

Apache Groovy 2.4.4 is the first and only supported release under the
Apache Software Foundation. It is strongly recommanded that all users
upgrade to this version. If you cannot upgrade or rely on an older,
unsupported version of Groovy, you can apply the following patch on the
MethodClosure class
(src/main/org/codehaus/groovy/runtime/MethodClosure.java):

 public class MethodClosure extends Closure {
+    private Object readResolve() {
+        throw new UnsupportedOperationException();
+    }

*Credit*

This vulnerability was discovered by:

   cpnrodzc7 working with HP's Zero Day Initiative

*References*

http://groovy-lang.org/security.html

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.