UBUNTU-CVE-2021-32751

Source
https://ubuntu.com/security/CVE-2021-32751
Import Source
https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2021/UBUNTU-CVE-2021-32751.json
JSON Data
https://api.test.osv.dev/v1/vulns/UBUNTU-CVE-2021-32751
Related
Published
2021-07-20T23:15:00Z
Modified
2024-10-15T14:08:10Z
Severity
  • 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
[none]
Details

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.

References

Affected packages

Ubuntu:Pro:16.04:LTS / gradle

Package

Name
gradle
Purl
pkg:deb/ubuntu/gradle?arch=src?distro=esm-apps/xenial

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

2.*

2.5-3
2.7-1
2.7-2
2.7-3
2.10-1

Ecosystem specific

{
    "ubuntu_priority": "medium"
}

Ubuntu:Pro:18.04:LTS / gradle

Package

Name
gradle
Purl
pkg:deb/ubuntu/gradle?arch=src?distro=esm-apps/bionic

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

3.*

3.2.1-3build2
3.2.1-4
3.2.1-5
3.4.1-4
3.4.1-6
3.4.1-7ubuntu1

4.*

4.4.1-5ubuntu2~18.04
4.4.1-5ubuntu2~18.04+esm1

Ecosystem specific

{
    "ubuntu_priority": "medium"
}

Ubuntu:20.04:LTS / gradle

Package

Name
gradle
Purl
pkg:deb/ubuntu/gradle?arch=src?distro=focal

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

4.*

4.4.1-8
4.4.1-9
4.4.1-10

Ecosystem specific

{
    "ubuntu_priority": "medium"
}

Ubuntu:22.04:LTS / gradle

Package

Name
gradle
Purl
pkg:deb/ubuntu/gradle?arch=src?distro=jammy

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

4.*

4.4.1-13

Ecosystem specific

{
    "ubuntu_priority": "medium"
}

Ubuntu:24.10 / gradle

Package

Name
gradle
Purl
pkg:deb/ubuntu/gradle?arch=src?distro=oracular

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

4.*

4.4.1-20
4.4.1-20build1

Ecosystem specific

{
    "ubuntu_priority": "medium"
}

Ubuntu:24.04:LTS / gradle

Package

Name
gradle
Purl
pkg:deb/ubuntu/gradle?arch=src?distro=noble

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

4.*

4.4.1-18
4.4.1-20

Ecosystem specific

{
    "ubuntu_priority": "medium"
}