CVSS: 6.6EPSS: 0%CPEs: 1EXPL: 0CVE-2022-31156 – Gradle's dependency verification can ignore checksum verification when signature verification cannot be performed
https://notcve.org/view.php?id=CVE-2022-31156
Gradle is a build tool. Dependency verification is a security feature in Gradle Build Tool that was introduced to allow validation of external dependencies either through their checksum or cryptographic signatures. In versions 6.2 through 7.4.2, there are some cases in which Gradle may skip that verification and accept a dependency that would otherwise fail the build as an untrusted external artifact. This can occur in two ways. When signature verification is disabled but the verification metadata contains entries for dependencies that only have a `gpg` element but no `checksum` element. • https://docs.gradle.org/7.5/release-notes.html https://github.com/gradle/gradle/security/advisories/GHSA-j6wc-xfg8-jx2j • CWE-347: Improper Verification of Cryptographic Signature CWE-829: Inclusion of Functionality from Untrusted Control Sphere •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-23630 – Dependency verification bypass in Gradle
https://notcve.org/view.php?id=CVE-2022-23630
Gradle is a build tool with a focus on build automation and support for multi-language development. In some cases, Gradle may skip that verification and accept a dependency that would otherwise fail the build as an untrusted external artifact. This occurs when dependency verification is disabled on one or more configurations and those configurations have common dependencies with other configurations that have dependency verification enabled. If the configuration that has dependency verification disabled is resolved first, Gradle does not verify the common dependencies for the configuration that has dependency verification enabled. Gradle 7.4 fixes that issue by validating artifacts at least once if they are present in a resolved configuration that has dependency verification active. • https://docs.gradle.org/7.4/release-notes.html https://github.com/gradle/gradle/commit/88ab9b652933bc3b2e3161b31ad8b8f4f0516351 https://github.com/gradle/gradle/security/advisories/GHSA-9pf5-88jw-3qgr • CWE-829: Inclusion of Functionality from Untrusted Control Sphere •
CVSS: 8.5EPSS: 1%CPEs: 1EXPL: 3CVE-2021-32751 – Arbitrary code execution via specially crafted environment variables
https://notcve.org/view.php?id=CVE-2021-32751
Gradle is a build tool with a focus on build automation. In versions prior to 7.2, start scripts generated by the `application` plugin and the `gradlew` script are both vulnerable to arbitrary code execution when an attacker is able to change environment variables for the user running the script. This may impact those who use `gradlew` on Unix-like systems or use the scripts generated by Gradle in thieir application on Unix-like systems. For this vulnerability to be exploitable, an attacker needs to be able to set the value of particular environment variables and have those environment variables be seen by the vulnerable scripts. This issue has been patched in Gradle 7.2 by removing the use of `eval` and requiring the use of the `bash` shell. • https://github.com/gradle/gradle/security/advisories/GHSA-6j2p-252f-7mw8 https://medium.com/dot-debug/the-perils-of-bash-eval-cc5f9e309cae https://mywiki.wooledge.org/BashFAQ/048 • CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') •