CVE-2021-29427

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.

• CWE-829

• https://docs.gradle.org/7.0/release-notes.html#security-advisoriesRelease Notes, Vendor Advisory
• https://github.com/gradle/gradle/security/advisories/GHSA-jvmj-rh6q-x395Exploit, Third Party Advisory
• https://docs.gradle.org/7.0/release-notes.html#security-advisoriesRelease Notes, Vendor Advisory
• https://github.com/gradle/gradle/security/advisories/GHSA-jvmj-rh6q-x395Exploit, Third Party Advisory

Published

Apr 13, 2021

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2021-29416An issue was discovered in PortSwigger Burp Suite before 202…6.5
• CVE-2021-29417gitjacker before 0.1.0 allows remote attackers to execute ar…9.8
• CVE-2021-29418The netmask package before 2.0.1 for Node.js mishandles cert…5.3
• CVE-2021-29421models/metadata.py in the pikepdf package 1.3.0 through 2.9.…7.5
• CVE-2021-29424The Net::Netmask module before 2.0000 for Perl does not prop…7.5
• CVE-2021-29425In Apache Commons IO before 2.7, When invoking the method Fi…4.8
• CVE-2021-29428In Gradle before version 7.0, on Unix-like systems, the syst…7.8
• CVE-2021-29429In Gradle before version 7.0, files created with open permis…5.5
• CVE-2021-29430Sydent is a reference Matrix identity server. Sydent does no…7.5
• CVE-2021-29431Sydent is a reference Matrix identity server. Sydent can be …6.5
• CVE-2021-29432Sydent is a reference matrix identity server. A malicious us…5.7
• CVE-2021-29433Sydent is a reference Matrix identity server. In Sydent vers…4.3