Arbitrary code execution via shell eval expansion
Published Jul 20, 2021 · Updated Aug 3, 2024
Command injection in Gradle Build Tool before 7.2 allows attackers to execute arbitrary code through Unix-like launch scripts. The gradlew and application-plugin start scripts pass JAVA_OPTS, GRADLE_OPTS, or application-specific option variables through shell eval, causing embedded command substitutions to run as the script user. Exploitation requires control of an environment variable visible to a user who later invokes the vulnerable wrapper or generated start script.
Summary
What happened
Command injection in Gradle Build Tool before 7.2 allows attackers to execute arbitrary code through Unix-like launch scripts. The gradlew and application-plugin start scripts pass JAVA_OPTS, GRADLE_OPTS, or application-specific option variables through shell eval, causing embedded command substitutions to run as the script user. Exploitation requires control of an environment variable visible to a user who later invokes the vulnerable wrapper or generated start script.
The record
- CVE
- CVE-2021-32751
- Published
- Jul 20, 2021
- Updated
- Aug 3, 2024
- Vendor
- Gradle, Inc.
- Product
- Gradle Build Tool
- Classifications
- CWE-78, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 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=< 7.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
- Gradle environment-variable command-injection exampleproof 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