CVE-2021-29427: Repository content filters do not work in Settings pluginManagement
First published: Fri Apr 09 2021(Updated: )
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.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gradle Gradle | >=5.1<7.0 | |
| Quarkus Quarkus | <=2.2.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
- https://docs.gradle.org/7.0/release-notes.html#security-advisories
- https://github.com/gradle/gradle/security/advisories/GHSA-jvmj-rh6q-x395
- https://access.redhat.com/errata/RHSA-2022:4623
- https://access.redhat.com/security/cve/cve-2021-29427
- https://bugzilla.redhat.com/show_bug.cgi?id=1949638
- https://www.cve.org/CVERecord?id=CVE-2021-29427 https://nvd.nist.gov/vuln/detail/CVE-2021-29427
Frequently Asked Questions
What is CVE-2021-29427?
CVE-2021-29427 is a vulnerability in Gradle versions 5.1 to 7.0 that can result in information disclosure and/or dependency poisoning.
What is the severity of CVE-2021-29427?
CVE-2021-29427 has a severity level of high.
How does the vulnerability in CVE-2021-29427 occur?
The vulnerability in CVE-2021-29427 occurs due to a security control issue in Gradle's repository content filtering, which can lead to unauthorized access to dependencies and potential information disclosure.
What software versions are affected by CVE-2021-29427?
CVE-2021-29427 affects Gradle versions 5.1 to 7.0 and Quarkus versions up to 2.2.3.
How can CVE-2021-29427 be mitigated?
To mitigate CVE-2021-29427, it is recommended to upgrade Gradle to a version beyond 7.0 and Quarkus to a version beyond 2.2.3, as well as review the repositories used for dependency resolution.
- collector/redhat-cve
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2021-29427
- agent/references
- agent/severity
- agent/weakness
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/last-modified-date
- agent/description
- agent/event
- agent/tags
- agent/trending
- vendor/gradle
- canonical/gradle gradle
- version/gradle gradle/5.1
- vendor/quarkus
- canonical/quarkus quarkus
- version/quarkus quarkus/2.2.3