Bug 1949643 (CVE-2021-29428) - CVE-2021-29428 gradle: local privilege escalation through system temporary directory
Summary: CVE-2021-29428 gradle: local privilege escalation through system temporary di...
Alias: CVE-2021-29428
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 1949646
TreeView+ depends on / blocked
Reported: 2021-04-14 17:40 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-05-18 14:33 UTC (History)
56 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-05-18 14:33:52 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:4623 0 None None None 2022-05-18 10:56:19 UTC

Description Guilherme de Almeida Suckevicz 2021-04-14 17:40:05 UTC
In Gradle before version 7.0, on Unix-like systems, the system temporary directory can be created with open permissions that allow multiple users to create and delete files within it. Gradle builds could be vulnerable to a local privilege escalation from an attacker quickly deleting and recreating files in the system temporary directory. This vulnerability impacted builds using precompiled script plugins written in Kotlin DSL and tests for Gradle plugins written using ProjectBuilder or TestKit. If you are on Windows or modern versions of macOS, you are not vulnerable. If you are on a Unix-like operating system with the "sticky" bit set on your system temporary directory, you are not vulnerable. The problem has been patched and released with Gradle 7.0. As a workaround, on Unix-like operating systems, ensure that the "sticky" bit is set. This only allows the original user (or root) to delete a file. If you are unable to change the permissions of the system temporary directory, you can move the Java temporary directory by setting the System Property `java.io.tmpdir`. The new path needs to limit permissions to the build user only. For additional details refer to the referenced GitHub Security Advisory.


Comment 4 Jonathan Christison 2021-04-30 17:54:30 UTC
Marking Camel K and Camel Quarkus as having a low impact, although both products ship indirectly vulnerable artifacts (gradle-wrapper) these artifacts are not available for use by application developers and are not used during the build of either product.

Comment 6 Todd Cullum 2021-05-04 17:49:27 UTC

Red Hat CodeReady Studio 12 is not affected by this vulnerability because it does not ship the vulnerable code.

Comment 9 errata-xmlrpc 2022-05-18 10:56:15 UTC
This issue has been addressed in the following products:

  Red Hat build of Quarkus 2.7.5

Via RHSA-2022:4623 https://access.redhat.com/errata/RHSA-2022:4623

Comment 10 Product Security DevOps Team 2022-05-18 14:33:50 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


Note You need to log in before you can comment on or make changes to this bug.