Arbitrary code execution via invoked project build tools
Published Nov 30, 2022 · Updated Apr 24, 2025
Code injection in Snyk CLI before 1.1064.0 allows attackers to execute arbitrary code by inducing a user to scan a malicious project. During dependency analysis, the CLI invokes project build tools that execute commands embedded in files such as build.gradle or gradle-wrapper.jar with the CLI process's privileges. Attackers must persuade a user to download and scan the project; IDE-triggered scans also require the folder to be trusted where a trust feature applies.
Summary
What happened
Code injection in Snyk CLI before 1.1064.0 allows attackers to execute arbitrary code by inducing a user to scan a malicious project. During dependency analysis, the CLI invokes project build tools that execute commands embedded in files such as build.gradle or gradle-wrapper.jar with the CLI process's privileges. Attackers must persuade a user to download and scan the project; IDE-triggered scans also require the folder to be trusted where a trust feature applies.
The record
- CVE
- CVE-2022-24441
- Published
- Nov 30, 2022
- Updated
- Apr 24, 2025
- Vendor
- Snyk
- Product
- Snyk CLI
- Classifications
- CWE-77, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 30, 2022CVE publishedPublication date reported by the CVE source.
- Apr 24, 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=unspecified <1.1064.0
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
- Imperva malicious-project exploitation researchproof of concept · demonstrated
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