CVE-2021-29429: In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by Gradle. Some builds could be vulnerable to a local information disclosure. Remote files accessed through TextResourceFactory are downloaded into the system temporary directory first. Sensitive information contained in these files can be exposed to other local users on the same system. If you do not use the `TextResourceFactory` API, you are not vulnerable. As of Gradle 7.0, uses of the system temporary directory have been moved to the Gradle User Home directory. By default, this directory is restricted to the user running the build. As a workaround, set a more restrictive umask that removes read access to other users. When files are created in the system temporary directory, they will not be accessible to other users. If you are unable to change your system's umask, you can move the Java temporary directory by setting the System Property `java.io.tmpdir`. The new path needs to limit permissions to the build user only. Fixed in 7.0, please bump.
Gradle 7 is in ::java. We currently have gradle 6.3 in ::gentoo, but no consumer (nothing in ::gentoo depends on dev-java/gradle). Furthermore, gradle 7 removed support for some deprecated directives. This means that, even if we had gradle 7 in ::gentoo, and even if we had a consumer in ::gentoo, then we probably would still need a gradle version < 7 in ::gentoo to compile the consumer. But this is all hypothetical. I would be fine with removing gradle from ::gentoo for now. Or to provide a PR for adding gradle 7 to gentoo.
CVE-2021-29427: In Gradle from version 5.1 and before version 7.0 there is a vulnerability which can lead to information disclosure and/or dependency poisoning. Repository content filtering is a security control Gradle introduced to help users specify what repositories are used to resolve specific dependencies. This feature was introduced in the wake of the "A Confusing Dependency" blog post. In some cases, Gradle may ignore content filters and search all repositories for dependencies. This only occurs when repository content filtering is used from within a `pluginManagement` block in a settings file. This may change how dependencies are resolved for Gradle plugins and build scripts. For builds that are vulnerable, there are two risks: 1) Information disclosure: Gradle could make dependency requests to repositories outside your organization and leak internal package identifiers. 2) Dependency poisoning/Dependency confusion: Gradle could download a malicious binary from a repository outside your organization due to name squatting. For a full example and more details refer to the referenced GitHub Security Advisory. The problem has been patched and released with Gradle 7.0. Users relying on this feature should upgrade their build as soon as possible. As a workaround, users may use a company repository which has the right rules for fetching packages from public repositories, or use project level repository content filtering, inside `buildscript.repositories`. This option is available since Gradle 5.1 when the feature was introduced.
Another, sorry for the noise everyone. CVE-2021-29428: In Gradle before version 7.0, on Unix-like systems, the system temporary directory can be created with open permissions that allow multiple users to create and delete files within it. Gradle builds could be vulnerable to a local privilege escalation from an attacker quickly deleting and recreating files in the system temporary directory. This vulnerability impacted builds using precompiled script plugins written in Kotlin DSL and tests for Gradle plugins written using ProjectBuilder or TestKit. If you are on Windows or modern versions of macOS, you are not vulnerable. If you are on a Unix-like operating system with the "sticky" bit set on your system temporary directory, you are not vulnerable. The problem has been patched and released with Gradle 7.0. As a workaround, on Unix-like operating systems, ensure that the "sticky" bit is set. This only allows the original user (or root) to delete a file. If you are unable to change the permissions of the system temporary directory, you can move the Java temporary directory by setting the System Property `java.io.tmpdir`. The new path needs to limit permissions to the build user only. For additional details refer to the referenced GitHub Security Advisory.
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. There are a few workarounds available. For CI/CD systems using the Gradle build tool, one may ensure that untrusted users are unable to change environment variables for the user that executes `gradlew`. If one is unable to upgrade to Gradle 7.2, one may generate a new `gradlew` script with Gradle 7.2 and use it for older versions of Gradle. Fpplications using start scripts generated by Gradle, one may ensure that untrusted users are unable to change environment variables for the user that executes the start script. A vulnerable start script could be manually patched to remove the use of `eval` or the use of environment variables that affect the application's command-line. If the application is simple enough, one may be able to avoid the use of the start scripts by running the application directly with Java command.
Package list is empty or all packages have requested keywords.
CVE-2022-23630 (https://github.com/gradle/gradle/security/advisories/GHSA-9pf5-88jw-3qgr): 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. For users who cannot update either do not use `ResolutionStrategy.disableDependencyVerification()` and do not use plugins that use that method to disable dependency verification for a single configuration or make sure resolution of configuration that disable that feature do not happen in builds that resolve configuration where the feature is enabled. Fix in 7.4.
CVE-2022-31156 (https://docs.gradle.org/7.5/release-notes.html): https://github.com/gradle/gradle/security/advisories/GHSA-j6wc-xfg8-jx2j 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. When signature verification is enabled, the verification metadata contains entries for dependencies with a `gpg` element but there is no signature file on the remote repository. In both cases, the verification will accept the dependency, skipping signature verification and not complaining that the dependency has no checksum entry. For builds that are vulnerable, there are two risks. Gradle could download a malicious binary from a repository outside your organization due to name squatting. For those still using HTTP only and not HTTPS for downloading dependencies, the build could download a malicious library instead of the expected one. Gradle 7.5 patches this issue by making sure to run checksum verification if signature verification cannot be completed, whatever the reason. Two workarounds are available: Remove all `gpg` elements from dependency verification metadata if you disable signature validation and/or avoid adding `gpg` entries for dependencies that do not have signature files.
Still needs cleanup, it seems. No GLSA for unstable-only packages anyway.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=00abccd0eccaceee738ae9746e0bf5cf1677d96d commit 00abccd0eccaceee738ae9746e0bf5cf1677d96d Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2024-01-07 09:04:35 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2024-01-07 09:16:25 +0000 dev-java/gradle-bin: drop versions Bug: https://bugs.gentoo.org/782694 Bug: https://bugs.gentoo.org/917402 Bug: https://bugs.gentoo.org/905329 Signed-off-by: Florian Schmaus <flow@gentoo.org> dev-java/gradle-bin/Manifest | 9 ----- dev-java/gradle-bin/gradle-bin-6.8.3.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-7.1.1.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-7.2.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-7.3.3.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-7.4.2.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-7.5.1.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-7.6.1.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-8.0.2.ebuild | 61 ----------------------------- dev-java/gradle-bin/gradle-bin-8.1.1.ebuild | 61 ----------------------------- 10 files changed, 558 deletions(-)
