Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-rcjj-h6gh-jf3r

Information Disclosure in Apache Groovy

CVSS 5.5 MediumEPSS 0.010 · 63rd percentile

Published by the GitHub Advisory Database at 9 Dec 2020, 19:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.codehaus.groovy:groovyMaven>=2.0.0, <2.4.21 || >=2.5.0, <2.5.14 || >=3.0.0, <3.0.72.4.21, 2.5.14, 3.0.7
org.codehaus.groovy:groovy-allMaven>=2.0.0, <2.4.21 || >=2.5.0, <2.5.14 || >=3.0.0, <3.0.72.4.21, 2.5.14, 3.0.7
Identifiers
GHSA-rcjj-h6gh-jf3r · CVE-2020-17521
Weakness (CWE)
CWE-379
Tags
Published
9 Dec 2020
Updated
17 Oct 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Groovy versions 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 are affected, as are the groovy and groovy-all packages in those ranges. The source gives few details: the temporary directory extension methods used an insecure, now superseded JDK method that may be insecure on some operating systems in some contexts, and only users of those methods are affected. Upgrade to groovy 2.4.21, 2.5.14, or 3.0.7, or to 4.0.0-alpha-2 for the 4.0 line.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.5 Medium 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.