Dependency verification bypass in Gradle

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.

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

从非可信控制范围包含功能例程

Gradle 安全漏洞

Gradle是美国Gradle公司的一套基于JVM的项目构建工具，它支持maven、Ivy仓库等。 Gradle 存在安全漏洞，该漏洞源于在某些情况下，Gradle可能会跳过验证，并接受一个依赖项，否则这个依赖项会作为一个不可信的外部构件导致构建失败。当在一个或多个配置上禁用依赖验证，并且这些配置与其他启用依赖验证的配置有共同依赖时，就会发生这种情况。如果首先解析的配置中禁用了依赖项验证，那么Gradle不会验证配置中常见的依赖项。

N/A

其他