A security issue has been found 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 a Unix-like operating system with the "sticky" bit set on your system temporary directory, you are not vulnerable.
A security issue has been found 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 a Unix-like operating system with the "sticky" bit set on your system temporary directory, you are not vulnerable.
https://github.com/gradle/gradle/security/advisories/GHSA-89qm-pxvm-p336
By default, the /tmp directory on Arch Linux is created with the sticky bit set and is therefore not vulnerable to this issue. However, systems with custom temporary directory setups might still be affected.
Vulmon