CVE-2021-32751

一、漏洞信息
 漏洞编号：[CVE-2021-32751](https://nvd.nist.gov/vuln/detail/CVE-2021-32751)
 漏洞归属组件：[gradle](https://gitee.com/src-openeuler/gradle)
 漏洞归属的版本：4.4.1
 CVSS V3.0分值：
  BaseScore：7.5 High
  Vector：CVSS：3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
 漏洞简述：
  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.
 漏洞公开时间：2021-07-21 07:15
 漏洞创建时间：2024-10-13 01:59:43
 漏洞详情参考链接：
  https://nvd.nist.gov/vuln/detail/CVE-2021-32751
<details>
<summary>更多参考(点击展开)</summary>

| 参考来源 | 参考链接 | 来源链接 |
| ------- | -------- | -------- |
| github | https://github.com/gradle/gradle/security/advisories/GHSA-6j2p-252f-7mw8 |  |
| mywiki |  https://mywiki.wooledge.org/BashFAQ/048 |  |
| medium |  https://medium.com/dot-debug/the-perils-of-bash-eval-cc5f9e309cae |  |

</details>

漏洞分析指导链接：
  https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
 漏洞数据来源:
  openBrain开源漏洞感知系统
 漏洞补丁信息：
  <details>
<summary>详情(点击展开)</summary>

无
</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.             
 openEuler评分：
  7.5
 Vector：CVSS：3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
 受影响版本排查(受影响/不受影响)：
  1.master(4.4.1):受影响
2.openEuler-20.03-LTS-SP4(4.4.1):受影响
3.openEuler-22.03-LTS-SP3(4.4.1):受影响
4.openEuler-22.03-LTS-SP4(4.4.1):受影响
5.openEuler-24.03-LTS(4.4.1):受影响
6.openEuler-24.03-LTS-Next(4.4.1):受影响
7.openEuler-24.03-LTS-SP1(4.4.1):受影响
8.openEuler-24.03-LTS-SP2(4.4.1):受影响

修复是否涉及abi变化(是/否)：
  1.master(4.4.1):否
2.openEuler-20.03-LTS-SP4(4.4.1):否
3.openEuler-22.03-LTS-SP3(4.4.1):否
4.openEuler-22.03-LTS-SP4(4.4.1):否
5.openEuler-24.03-LTS(4.4.1):否
6.openEuler-24.03-LTS-Next(4.4.1):否
7.openEuler-24.03-LTS-SP1(4.4.1):否
8.openEuler-24.03-LTS-SP2(4.4.1):否

原因说明：
  1.master(4.4.1):正常修复
2.openEuler-20.03-LTS-SP4(4.4.1):正常修复
3.openEuler-22.03-LTS-SP3(4.4.1):正常修复
4.openEuler-22.03-LTS-SP4(4.4.1):正常修复
5.openEuler-24.03-LTS(4.4.1):正常修复
6.openEuler-24.03-LTS-Next(4.4.1):正常修复
7.openEuler-24.03-LTS-SP1(4.4.1):正常修复
8.openEuler-24.03-LTS-SP2(4.4.1):正常修复

src-openEuler/gradle
关闭

内容风险标识

评论 (7)

src-openEuler/gradle关闭 .gitee-modal { width: 500px !important; }

内容风险标识

CVE-2021-32751

评论 (7)

搜索帮助

src-openEuler/gradle
关闭