CVE and update status of the FreeBSD ports tree4,526 unaddressed CVEs in 616 portsAll times are CET

CVE details

CVE-2021-32751

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.

Score
7.5 high
Published
2021-07-20
Links
NVD · cve.org

Affected ports (3)

PortPackageVersionStatusMaintainer
devel/gradle5gradle55.0_3unaddressedyuri@FreeBSD.org
devel/gradle62gradle626.2.2_3unaddressedyuri@FreeBSD.org
devel/gradle6gradle66.9.4_2possibly backportedports@FreeBSD.org

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>gradle5</name>
	<range><lt>7.2</lt></range>
      </package>
      <package>
	<name>gradle62</name>
	<range><lt>7.2</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2021-32751</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2021-32751</url>
    </references>
    <dates>
      <discovery>2021-07-20</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>