Skip to content

Information Disclosure in Apache Groovy

Moderate severity GitHub Reviewed Published Dec 9, 2020 to the GitHub Advisory Database • Updated Oct 17, 2024

Package

maven org.codehaus.groovy:groovy (Maven)

Affected versions

>= 2.0.0, < 2.4.21
>= 2.5.0, < 2.5.14
>= 3.0.0, < 3.0.7

Patched versions

2.4.21
2.5.14
3.0.7
maven org.codehaus.groovy:groovy-all (Maven)
>= 2.0.0, < 2.4.21
>= 2.5.0, < 2.5.14
>= 3.0.0, < 3.0.7
2.4.21
2.5.14
3.0.7

Description

Apache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2.

References

Published by the National Vulnerability Database Dec 7, 2020
Reviewed Dec 9, 2020
Published to the GitHub Advisory Database Dec 9, 2020
Last updated Oct 17, 2024

Severity

Moderate

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
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.069%
(32nd percentile)

Weaknesses

CVE ID

CVE-2020-17521

GHSA ID

GHSA-rcjj-h6gh-jf3r

Source code

Credits

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