CVE-2023-35947 Path traversal vulnerabilities in handling of Tar archives in Gradle

Medium 6.9 Published Updated

Attackers can overwrite files or read sensitive data via malicious Tar archives in Gradle, requiring an upgrade to secure the build process.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2023-35947?

CVE-2023-35947 is a medium-severity path traversal vulnerability in gradle, published on 30 Jun 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

Gradle is a build tool with a focus on build automation and support for multi-language development. In affected versions when unpacking Tar archives, Gradle did not check that files could be written outside of the unpack location. This could lead to important files being overwritten anywhere the Gradle process has write permissions. For a build reading Tar entries from a Tar archive, this issue could allow Gradle to disclose information from sensitive files through an arbitrary file read. To exploit this behavior, an attacker needs to either control the source of an archive already used by the build or modify the build to interact with a malicious archive. It is unlikely that this would go unnoticed. A fix has been released in Gradle 7.6.2 and 8.2 to protect against this vulnerability. Starting from these versions, Gradle will refuse to handle Tar archives which contain path traversal elements in a Tar entry name. Users are advised to upgrade. There are no known workarounds for this vulnerability.

### Impact

This is a path traversal vulnerability when Gradle deals with Tar archives, often referenced as TarSlip, a variant of ZipSlip.

* When unpacking Tar archives, Gradle did not check that files could be written outside of the unpack location. This could lead to important files being overwritten anywhere the Gradle process has write permissions. * For a build reading Tar entries from a Tar archive, this issue could allow Gradle to disclose information from sensitive files through an arbitrary file read.

To exploit this behavior, an attacker needs to either control the source of an archive already used by the build or modify the build to interact with a malicious archive. It is unlikely that this would go unnoticed.

Gradle uses Tar archives for its [Build Cache](https://docs.gradle.org/current/userguide/build_cache.html). These archives are safe when created by Gradle. But if an attacker had control of a remote build cache server, they could inject malicious build cache entries that leverage this vulnerability. This attack vector could also be exploited if a man-in-the-middle can be performed between the remote cache and the build.

### Patches

A fix has been released in Gradle 7.6.2 and 8.2 to protect against this vulnerability. Starting from these versions, Gradle will refuse to handle Tar archives which contain path traversal elements in a Tar entry name.

It is recommended that users upgrade to a patched version.

### Workarounds

There is no workaround.

* If your build deals with Tar archives that you do not fully trust, you need to inspect them to confirm they do not attempt to leverage this vulnerability. * If you use the Gradle remote build cache, make sure only trusted parties have write access to it and that connections to the remote cache are properly secured.

### References

* [CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')](https://cwe.mitre.org/data/definitions/22.html) * [Gradle Build Cache](https://docs.gradle.org/current/userguide/build_cache.html) * [ZipSlip](https://security.snyk.io/research/zip-slip-vulnerability)

Weakness: CWE-22

Which versions are affected by CVE-2023-35947?

1 open source package ship an affected version, including gradle. It affects 1 product.

PackageAffectedFixed in
gradle BitnamiAll versions7.6.2, 8.2.0
Linux distribution packages (15)
gradle SUSE:Enterprise Storage 7.1All versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Module for Development Tools 15 SP5All versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Module for Development Tools 15 SP6All versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Server 15 SP2-LTSSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Server 15 SP3-LTSSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Server 15 SP4-LTSSAll versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Server for SAP Applications 15 SP2All versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Server for SAP Applications 15 SP3All versions4.4.1-150200.3.27.1
gradle SUSE:Linux Enterprise Server for SAP Applications 15 SP4All versions4.4.1-150200.3.27.1
gradle openSUSE:Leap 15.5All versions4.4.1-150200.3.27.1
gradle openSUSE:Leap 15.6All versions4.4.1-150200.3.27.1

Products include Gradle Gradle.

How do I fix CVE-2023-35947?

Upgrade gradle to a fixed version for your release line: 7.6.2 or 8.2.0.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2023-35947 being exploited?

There is no known exploitation of CVE-2023-35947 in the wild and no public exploit code.

Sources

Also known as BELL-CVE-2023-35947, BIT-gradle-2023-35947, DEBIAN-CVE-2023-35947, GHSA-84mw-qh6q-v842, SUSE-SU-2024:3923-1, UBUNTU-CVE-2023-35947.

Is CVE-2023-35947 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free