# CVE-2020-17521: Information Disclosure in Apache Groovy > Attackers can exploit insecure temporary directory creation in Apache Groovy to access or modify files, requiring an upgrade to patched versions. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Dec 2020 - **Updated:** 8 Oct 2026 - **Also known as:** DEBIAN-CVE-2020-17521, GHSA-rcjj-h6gh-jf3r, SUSE-SU-2020:3917-1, UBUNTU-CVE-2020-17521, openSUSE-SU-2020:2367-1, openSUSE-SU-2024:10823-1 ## What is CVE-2020-17521? CVE-2020-17521 is a medium-severity path traversal vulnerability in Netapp Snapcenter, published on 7 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official 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. ## Which versions are affected by CVE-2020-17521? 12 open source packages ship an affected version, including org.codehaus.groovy:groovy and org.codehaus.groovy:groovy-all. It affects 21 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.codehaus.groovy:groovy` | Maven | From 2.0.0 | 2.4.21 | | `org.codehaus.groovy:groovy` | Maven | From 2.0.0 | 2.4.21 | | `org.codehaus.groovy:groovy` | Maven | From 2.5.0 | 2.5.14 | | `org.codehaus.groovy:groovy` | Maven | From 2.5.0 | 2.5.14 | | `org.codehaus.groovy:groovy` | Maven | From 3.0.0 | 3.0.7 | | `org.codehaus.groovy:groovy` | Maven | From 3.0.0 | 3.0.7 | | `org.codehaus.groovy:groovy-all` | Maven | From 2.0.0 | 2.4.21 | | `org.codehaus.groovy:groovy-all` | Maven | From 2.0.0 | 2.4.21 | | `org.codehaus.groovy:groovy-all` | Maven | From 2.5.0 | 2.5.14 | | `org.codehaus.groovy:groovy-all` | Maven | From 2.5.0 | 2.5.14 | | `org.codehaus.groovy:groovy-all` | Maven | From 3.0.0 | 3.0.7 | | `org.codehaus.groovy:groovy-all` | Maven | From 3.0.0 | 3.0.7 | | `groovy` | SUSE:Linux Enterprise Module for Development Tools 15 SP2 | All versions | 2.4.21-3.3.2 | | `groovy` | openSUSE:Leap 15.2 | All versions | 2.4.21-lp152.2.3.2 | | `groovy` | openSUSE:Tumbleweed | All versions | 2.4.21-2.3 | Products: Apache Atlas, Apache Groovy, Netapp Snapcenter, Oracle Agile Engineering Data Management, Oracle Agile Plm Mcad Connector, Oracle Agile Product Lifecycle Management, Oracle Business Process Management Suite, Oracle Communications Brm - Elastic Charging Engine, Oracle Communications Diameter Signaling Router, Oracle Communications Evolved Communications Application Server, Oracle Communications Services Gatekeeper, Oracle Healthcare Data Repository, Oracle Hospitality Opera 5, Oracle Ilearning, Oracle Insurance Policy Administration, Oracle Jd Edwards Enterpriseone Orchestrator, Oracle Primavera Gateway, Oracle Primavera Unifier, Oracle Retail Bulk Data Integration, Oracle Retail Merchandising System and 1 more. ## How do I fix CVE-2020-17521? Upgrade org.codehaus.groovy:groovy to a fixed version for your release line: 2.4.21, 2.5.14 or 3.0.7. ## Is CVE-2020-17521 being exploited? There is no known exploitation of CVE-2020-17521 in the wild and no public exploit code. ## Other vulnerabilities in Netapp Snapcenter - [CVE-2026-50622](https://insights.sbomify.com/CVE-2026-50622/): Apache Atlas: Missing Authorization on Admin Endpoints (high 8.8) - [CVE-2022-34271](https://insights.sbomify.com/CVE-2022-34271/): Apache Atlas: zip path traversal in import functionality (high 8.8) - [CVE-2026-40563](https://insights.sbomify.com/CVE-2026-40563/): Apache Atlas: Script injection allows access to unintended data (high 8.1) - [CVE-2016-8752](https://insights.sbomify.com/CVE-2016-8752/): Path Traversal in Apache Atlas (high 7.5) - [CVE-2017-3154](https://insights.sbomify.com/CVE-2017-3154/): Apache Atlas produces Stack trace in error response (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-17521 and fix it if it is affected. What it is: CVE-2020-17521 is a medium-severity path traversal vulnerability in Netapp Snapcenter, published on 7 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-17521 in the wild and no public exploit code. Affected packages and fixed versions: - org.codehaus.groovy:groovy (Maven): affected from 2.0.0; fixed in 2.4.21 - org.codehaus.groovy:groovy (Maven): affected from 2.0.0; fixed in 2.4.21 - org.codehaus.groovy:groovy (Maven): affected from 2.5.0; fixed in 2.5.14 - org.codehaus.groovy:groovy (Maven): affected from 2.5.0; fixed in 2.5.14 - org.codehaus.groovy:groovy (Maven): affected from 3.0.0; fixed in 3.0.7 - org.codehaus.groovy:groovy (Maven): affected from 3.0.0; fixed in 3.0.7 - org.codehaus.groovy:groovy-all (Maven): affected from 2.0.0; fixed in 2.4.21 - org.codehaus.groovy:groovy-all (Maven): affected from 2.0.0; fixed in 2.4.21 - org.codehaus.groovy:groovy-all (Maven): affected from 2.5.0; fixed in 2.5.14 - org.codehaus.groovy:groovy-all (Maven): affected from 2.5.0; fixed in 2.5.14 - org.codehaus.groovy:groovy-all (Maven): affected from 3.0.0; fixed in 3.0.7 - org.codehaus.groovy:groovy-all (Maven): affected from 3.0.0; fixed in 3.0.7 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-17521/ (Markdown: https://insights.sbomify.com/CVE-2020-17521/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-17521 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-17521 - OSV: https://osv.dev/vulnerability/CVE-2020-17521 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-17521/ Summaries are generated and may contain mistakes; the official description above is the record.