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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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. (CVE-2023-35946)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has a package installed that is affected by a vulnerability as referenced in the SUSE-SU-2024:3163-1 advisory.

    - CVE-2023-35946: Fixed a dependency issue leading the cache to write files into an unintended location.
    (bsc#1212930)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
257907	Linux Distros Unpatched Vulnerability : CVE-2023-35946	Nessus	Misc.	Local	medium
206755	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : gradle (SUSE-SU-2024:3163-1)	Nessus	SuSE Local Security Checks	Local	medium

Detections

Analytics

CVE-2023-35946

medium

Tenable Plugins

medium

medium