CVE-2022-23630 Dependency verification bypass in Gradle
Gradle may skip dependency verification for shared artifacts if one configuration disables it, allowing untrusted dependencies to be accepted.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-23630?
CVE-2022-23630 is a high-severity vulnerability in gradle, published on 10 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-829
Which versions are affected by CVE-2022-23630?
1 open source package ship an affected version, including gradle. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gradle Bitnami | From 6.2.0 | 7.3.4 |
Products include Gradle Gradle.
How do I fix CVE-2022-23630?
Upgrade gradle to 7.3.4 or later.
Is CVE-2022-23630 being exploited?
There is no known exploitation of CVE-2022-23630 in the wild and no public exploit code.
Other vulnerabilities in gradle
- CVE-2019-15052 Information disclosure in n/a
- CVE-2016-6199 Deserialization in n/a
- CVE-2021-29428 Local privilege escalation through system temporary directory
- CVE-2026-22816 Gradle fails to disable repositories which can expose builds to malicious artifacts
- CVE-2026-22865 Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts
Sources
Also known as BIT-gradle-2022-23630, GHSA-9pf5-88jw-3qgr, UBUNTU-CVE-2022-23630.