Skip to content

Deserialization of Untrusted Data in Groovy

Critical severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Oct 17, 2024

Package

maven org.codehaus.groovy:groovy (Maven)

Affected versions

>= 1.7.0, <= 2.4.7

Patched versions

2.4.8
maven org.codehaus.groovy:groovy-all (Maven)
>= 1.7.0, <= 2.4.7
2.4.8

Description

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.

References

Published by the National Vulnerability Database Jan 18, 2018
Published to the GitHub Advisory Database May 13, 2022
Reviewed Jul 6, 2022
Last updated Oct 17, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

3.302%
(91st percentile)

Weaknesses

CVE ID

CVE-2016-6814

GHSA ID

GHSA-xphj-m9cc-8fmq

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.