Deserialization of Untrusted Data in Groovy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.codehaus.groovy:groovy Maven |
|
|
| org.codehaus.groovy:groovy-all Maven |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| org.codehaus.groovy:groovy Maven |
|
|
| org.codehaus.groovy:groovy-all Maven |
|
|
When an application with unsupported Codehaus versions of Groovy from 1.7.0 to 2.4.3, Apache Groovy 2.4.4 to 2.4.7 on classpath uses standard Java serialization mechanisms, e.g. to communicate between servers or to store local data, it was 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 were subject to this vulnerability.
From the CVE record · mitre
Affected Groovy packages can execute code when an application deserializes a specially crafted object. This affects applications that use standard Java serialization for network communication or stored local data and do not isolate deserialization. The input does not specify whether authentication or user interaction is required.
Check applications using Maven org.codehaus.groovy:groovy or org.codehaus.groovy:groovy-all versions 1.7.0 through 2.4.7.