CVE-2022-23630: Dependency verification bypass in Gradle
First published: Thu Feb 10 2022(Updated: )
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.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gradle Gradle | >=6.2.0<=7.3.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2022-23630?
CVE-2022-23630 is a vulnerability in Gradle, a build tool with a focus on build automation and support for multi-language development.
What is the severity of CVE-2022-23630?
The severity of CVE-2022-23630 is high (7.5).
How does CVE-2022-23630 impact Gradle users?
CVE-2022-23630 may allow an attacker to bypass dependency verification and accept untrusted external artifacts, potentially leading to build failures or other security issues.
Which versions of Gradle are affected by CVE-2022-23630?
Gradle versions 6.2.0 to 7.3.3 are affected by CVE-2022-23630.
How can I fix CVE-2022-23630?
To fix CVE-2022-23630, upgrade to Gradle version 7.4 or later, which includes the necessary security patches.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/last-modified-date
- agent/remedy
- agent/author
- agent/severity
- agent/references
- agent/weakness
- agent/first-publish-date
- agent/description
- agent/tags
- agent/event
- vendor/gradle
- canonical/gradle gradle
- version/gradle gradle/6.2.0
- version/gradle gradle/7.3.3