Build dependency substitution via missing locking
Published Feb 25, 2022 · Updated Aug 3, 2024
Dependency integrity failure in JetBrains Kotlin before 1.6.0 allows remote attackers to substitute Multiplatform Gradle build dependencies. The Kotlin Gradle plugin lacked dependency-locking support for Multiplatform projects, allowing resolution to select an artifact or version that differed from a previously verified build. Exploitation requires control of a configured dependency source or its responses, and the bounded impact is unauthorized build-dependency substitution.
Summary
What happened
Dependency integrity failure in JetBrains Kotlin before 1.6.0 allows remote attackers to substitute Multiplatform Gradle build dependencies. The Kotlin Gradle plugin lacked dependency-locking support for Multiplatform projects, allowing resolution to select an artifact or version that differed from a previously verified build. Exploitation requires control of a configured dependency source or its responses, and the bounded impact is unauthorized build-dependency substitution.
The record
- CVE
- CVE-2022-24329
- Published
- Feb 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-829, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2022CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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