Vulnerability · Published Jul 20, 2021 · Assigned by GitHub_M

CVE-2021-32751Arbitrary code execution via specially crafted environment variables

High 7.5

In plain English

A high-severity OS command injection in gradle from gradle. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 2.7% (higher than 86% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High
Exploit odds (30 days)2.7%top 14.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

Gradle is a build tool with a focus on build automation. In versions prior to 7.2, start scripts generated by the `application` plugin and the `gradlew` script are both vulnerable to arbitrary code execution when an attacker is able to change environment variables for the user running the script. This may impact those who use `gradlew` on Unix-like systems or use the scripts generated by Gradle in thieir application on Unix-like systems. For this vulnerability to be exploitable, an attacker needs to be able to set the value of particular environment variables and have those environment variables be seen by the vulnerable scripts. This issue has been patched in Gradle 7.2 by removing the use of `eval` and requiring the use of the `bash` shell. There are a few workarounds available. For CI/CD systems using the Gradle build tool, one may ensure that untrusted users are unable to change environment variables for the user that executes `gradlew`. If one is unable to upgrade to Gradle 7.2, one may generate a new `gradlew` script with Gradle 7.2 and use it for older versions of Gradle. Fpplications using start scripts generated by Gradle, one may ensure that untrusted users are unable to change environment variables for the user that executes the start script. A vulnerable start script could be manually patched to remove the use of `eval` or the use of environment variables that affect the application's command-line. If the application is simple enough, one may be able to avoid the use of the start scripts by running the application directly with Java command.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Alpine:v3.20gradle7.2-r0ALPINE-CVE-2021-32751
Alpine:v3.21gradle7.2-r0ALPINE-CVE-2021-32751
Alpine:v3.22gradle7.2-r0ALPINE-CVE-2021-32751
Alpine:v3.23gradle7.2-r0ALPINE-CVE-2021-32751
Alpine:v3.24gradle7.2-r0ALPINE-CVE-2021-32751
Debian:12gradleno fix listedDEBIAN-CVE-2021-32751
Debian:13gradleno fix listedDEBIAN-CVE-2021-32751
Debian:14gradleno fix listedDEBIAN-CVE-2021-32751
Ubuntu:22.04:LTSgradleno fix listedUBUNTU-CVE-2021-32751
Ubuntu:24.04:LTSgradleno fix listedUBUNTU-CVE-2021-32751
Ubuntu:25.10gradleno fix listedUBUNTU-CVE-2021-32751
Ubuntu:26.04:LTSgradleno fix listedUBUNTU-CVE-2021-32751
Ubuntu:26.10gradleno fix listedUBUNTU-CVE-2021-32751

Affected products (as reported)

VendorProductVersions
gradle gradle < 7.2

Weakness: CWE-78 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

References