Build poisoning via ignored plugin repository filters
Published Apr 13, 2021 · Updated Aug 3, 2024
Dependency confusion in Gradle Build Tool 5.1 through 6.8.3 allows remote attackers to poison builds through untrusted repositories. Repository filtering inside the settings file's pluginManagement block is ignored during plugin and build-script dependency resolution, causing every configured repository to be queried. Exposure requires that configuration and an attacker-controlled matching package; it can leak internal package names or execute poisoned dependencies in the build.
Summary
What happened
Dependency confusion in Gradle Build Tool 5.1 through 6.8.3 allows remote attackers to poison builds through untrusted repositories. Repository filtering inside the settings file's pluginManagement block is ignored during plugin and build-script dependency resolution, causing every configured repository to be queried. Exposure requires that configuration and an attacker-controlled matching package; it can leak internal package names or execute poisoned dependencies in the build.
The record
- CVE
- CVE-2021-29427
- Published
- Apr 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Gradle, Inc.
- Product
- Gradle Build Tool
- Classifications
- CWE-829, T1195.001
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 5.1, <= 6.8.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo