p PatchFirst

CVE-2021-29428

CVE-2021-29428 · Local privilege escalation through system temporary directory

CVSS 8.8 · High · EPSS 0.5%

Compare with your installed version

Affected products and known fixed versions are public information. Compare them with your installed version.

  • gradleNo fix published
  • gradle Debian 12No fix published
  • gradle Debian 13No fix published
  • gradle Debian 14No fix published
  • and 8 more

Check the installed version:

dpkg-query -W -f='${source:Package} ${binary:Package} ${Version}\n' | awk '$1=="gradle"'

Assess your server’s risks

The free check gives you a rating and a risk summary by technology stack, without signing up. It does not answer whether this particular vulnerability affects you.

Monitoring matches public information against your servers’ software. Detailed findings for your servers include the order of updates.

curl -fsSL https://patchfirst.dev/check.sh | sh
Check your server for free →

Channels carry general technology news; monitoring reports new findings on your servers in your dashboard, through browser notifications, in Telegram or via a webhook.

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

Published
Updated

Fixes in distributions

  • SUSE-SU-2023:1867-1 · openSUSE Leap 15.4, SUSE Enterprise Storage 7, SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP3-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, SUSE Linux Enterprise Module for Development Tools 15 SP4, SUSE Linux Enterprise Real Time 15 SP3, SUSE Linux Enterprise Server 15 SP2-LTSS, SUSE Linux Enterprise Server 15 SP3-LTSS, SUSE Linux Enterprise Server for SAP Applications 15 SP2, SUSE Linux Enterprise Server for SAP Applications 15 SP3 ·

Stack: system

Affected products and versions

  • gradle

    Versions
    • < 7.0: Affected

    No fix published

  • gradle Debian 12

    Versions
    • 4.4.1-18
    • 4.4.1-19
    • 4.4.1-20
    • 4.4.1-21
    • 4.4.1-22
    • 4.4.1-23
    All versions (10)
    • 4.5.1-1
    • 4.6-1
    • 4.6-2
    • 4.6-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Debian 13

    Versions
    • 4.4.1-22
    • 4.4.1-23
    • 4.5.1-1
    • 4.6-1
    • 4.6-2
    • 4.6-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Debian 14

    Versions
    • 4.4.1-22
    • 4.4.1-23
    • 4.5.1-1
    • 4.6-1
    • 4.6-2
    • 4.6-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 16.04 LTS

    Versions
    • 2.5-3
    • 2.7-1
    • 2.7-2
    • 2.7-3
    • 2.10-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu Pro 18.04 LTS

    Versions
    • 3.2.1-3build2
    • 3.2.1-4
    • 3.2.1-5
    • 3.4.1-4
    • 3.4.1-6
    • 3.4.1-7ubuntu1
    All versions (8)
    • 4.4.1-5ubuntu2~18.04
    • 4.4.1-5ubuntu2~18.04+esm1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 20.04 LTS

    Versions
    • 4.4.1-8
    • 4.4.1-9
    • 4.4.1-10
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 22.04 LTS

    Versions
    • 4.4.1-13
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 24.04 LTS

    Versions
    • 4.4.1-18
    • 4.4.1-20
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 25.10

    Versions
    • 4.4.1-22
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 26.10

    Versions
    • 4.4.1-22ubuntu1
    • 4.4.1-23
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • gradle Ubuntu 26.04 LTS

    Versions
    • 4.4.1-22
    • 4.4.1-22build1
    • 4.4.1-22ubuntu1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →