Deserialization in Apache Groovy

CVE-2016-6814

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.172 (97.1th percentile), scored .

Moderate probability of exploitation in the next 30 days — watch for active exploitation reports. 97th percentile — 97.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2016-6814: held from 0.172 to 0.172.

EPSS over last 30 days · oldest: 0.172 · newest: 0.172 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2016-6814?
CVE-2016-6814 is a critical-severity vulnerability in Apache Groovy, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2018-01-18.
How severe is CVE-2016-6814?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2016-6814 known to be exploited?
9 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.