Abextm

**Name of the Vulnerable Software and Affected Versions** Gradle versions prior to 7.4 **Description** Gradle is a build tool with a focus on build automation and support for multi-language development. In some cases, Gradle may skip 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. The issue is fixed in Gradle 7.4 by validating artifacts at least once if they are present in a resolved configuration that has dependency verification active. **Recommendations** For versions prior to 7.4, do not use `ResolutionStrategy.disableDependencyVerification()` and do not use plugins that use that method to disable dependency verification for a single configuration. Alternatively, make sure the resolution of the configuration that disables this feature does not happen in builds that resolve configurations where the feature is enabled. At the moment, there is no information about other versions that contain a fix for this issue.