Dependency poisoning via skipped checksum fallback
Published Jul 14, 2022 · Updated Apr 23, 2025
Dependency verification bypass in Gradle Build Tool 6.2 through 7.4.2 allows attackers to introduce malicious build dependencies. For gpg-only metadata, the verifier accepts an artifact without a checksum when signatures are disabled or its remote signature file is absent. Exploitation requires control of a name-squatted repository artifact or interception of an HTTP repository connection, after which malicious code enters the build.
Summary
What happened
Dependency verification bypass in Gradle Build Tool 6.2 through 7.4.2 allows attackers to introduce malicious build dependencies. For gpg-only metadata, the verifier accepts an artifact without a checksum when signatures are disabled or its remote signature file is absent. Exploitation requires control of a name-squatted repository artifact or interception of an HTTP repository connection, after which malicious code enters the build.
The record
- CVE
- CVE-2022-31156
- Published
- Jul 14, 2022
- Updated
- Apr 23, 2025
- Vendor
- Gradle, Inc.
- Product
- Gradle Build Tool
- Classifications
- CWE-347, CWE-829, T1195.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 14, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=>= 6.2, <= 7.4.2
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