p PatchFirst

CVE-2023-35946

CVE-2023-35946 · Dependency cache path traversal in Gradle

CVSS 6.9 · Medium · EPSS 0.3%

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.

Gradle is a build tool with a focus on build automation and support for multi-language development. When Gradle writes a dependency into its dependency cache, it uses the dependency's coordinates to compute a file location. With specially crafted dependency coordinates, Gradle can be made to write files into an unintended location. The file may be written outside the dependency cache or over another file in the dependency cache. This vulnerability could be used to poison the dependency cache or overwrite important files elsewhere on the filesystem where the Gradle process has write permissions. Exploiting this vulnerability requires an attacker to have control over a dependency repository used by the Gradle build or have the ability to modify the build's configuration. It is unlikely that this would go unnoticed. A fix has been released in Gradle 7.6.2 and 8.2 to protect against this vulnerability. Gradle will refuse to cache dependencies that have path traversal elements in their dependency coordinates. It is recommended that users upgrade to a patched version. If you are unable to upgrade to Gradle 7.6.2 or 8.2, `dependency verification` will make this vulnerability more difficult to exploit.

Published
Updated

Fixes in distributions

  • SUSE-SU-2024:3163-1 · openSUSE Leap 15.5, openSUSE Leap 15.6, SUSE Linux Enterprise Module for Development Tools 15 SP5, SUSE Linux Enterprise Module for Development Tools 15 SP6 ·

Stack: system

Affected products and versions

  • gradle

    Versions
    • < 7.6.2: Affected
    • >= 8.0, < 8.2: 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 (13)
    • 4.5.1-1
    • 4.6-1
    • 4.6-2
    • 4.6-3
    • 4.6-4
    • 4.6-5
    • 4.7-1
    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
    All versions (9)
    • 4.6-4
    • 4.6-5
    • 4.7-1
    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
    All versions (9)
    • 4.6-4
    • 4.6-5
    • 4.7-1
    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 →