Directory Traversal Affecting gradle package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN12-GRADLE-5750265
- published2 Jul 2023
- disclosed30 Jun 2023
Introduced: 30 Jun 2023
CVE-2023-35946 (opens in a new tab)How to fix?
There is no fixed version for Debian:12 gradle.
NVD Description
Note: Versions mentioned in the description apply only to the upstream gradle package and not the gradle package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Gradle is a build tool with a focus on build automation and support for multi-language development. When Gradle writes a dependency into its dependency cache, it uses the dependency's coordinates to compute a file location. With specially crafted dependency coordinates, Gradle can be made to write files into an unintended location. The file may be written outside the dependency cache or over another file in the dependency cache. This vulnerability could be used to poison the dependency cache or overwrite important files elsewhere on the filesystem where the Gradle process has write permissions. Exploiting this vulnerability requires an attacker to have control over a dependency repository used by the Gradle build or have the ability to modify the build's configuration. 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. Gradle will refuse to cache dependencies that have path traversal elements in their dependency coordinates. It is recommended that users upgrade to a patched version. If you are unable to upgrade to Gradle 7.6.2 or 8.2, dependency verification will make this vulnerability more difficult to exploit.
References
- https://security-tracker.debian.org/tracker/CVE-2023-35946
- https://docs.gradle.org/current/userguide/dependency_verification.html
- https://github.com/gradle/gradle/commit/859eae2b2acf751ae7db3c9ffefe275aa5da0d5d
- https://github.com/gradle/gradle/commit/b07e528feb3a5ffa66bdcc358549edd73e4c8a12
- https://github.com/gradle/gradle/security/advisories/GHSA-2h6c-rv6q-494v
- https://security.netapp.com/advisory/ntap-20230731-0003/