Deserialization of Untrusted Data in Groovy
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-6814US | critical9.8 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://mail-archives.apache.org/mod_mbox/www-announce/201701.mbox/%3CCADRx3PMZ2hBCGDTY35zYXFGaDnjAs0tc5-upaVs6QN2sYUejyA%40mail.gmail.com%3EWEB
- http://rhn.redhat.com/errata/RHSA-2017-0272.htmlWEB
- http://www.oracle.com/technetwork/security-advisory/cpuapr2018-3678067.htmlWEB
- http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.htmlWEB
- http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.htmlWEB
- https://access.redhat.com/errata/RHSA-2017:0868WEB
- https://access.redhat.com/errata/RHSA-2017:2486WEB
- https://access.redhat.com/errata/RHSA-2017:2596WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan