p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in gradle

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für gradle: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3

  1. CVE-2023-26053

    Mittel · CVSS 6.6EPSS 0,99%Korrektur verfügbar

    Gradle usage of long IDs for PGP keys opens potential for collision attacks

    Gradle is a build tool with a focus on build automation and support for multi-language development. This is a collision attack on long IDs (64bits) for PGP keys. Users of dependency verification in Gradle are vulnerable if they use long IDs for PGP keys in a `trusted-key` or `pgp` element in their dependency verification metadata file. The fix is to fail dependency verification if anything but a fingerprint is used in a trust element in dependency verification metadata. The problem is fixed in Gradle 8.0 and above. The problem is also patched in Gradle 6.9.4 and 7.6.1. As a workaround, use only full fingerprint IDs for `trusted-key` or `pgp`

    • Auf 7.6.1-r0 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2021-32751

    Hoch · CVSS 7.5EPSS 2,71%Korrektur verfügbar

    Arbitrary code execution via specially crafted environment variables

    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 h

    • Auf 7.2-r0 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2020-11979

    Hoch · CVSS 7.5EPSS 7,76%Korrektur verfügbar

    CVE-2020-11979

    As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them. Unfortunately the fixcrlf task deleted the temporary file and created a new one without said protection, effectively nullifying the effort. This would still allow an attacker to inject modified source files into the build process.

    • Auf 6.8.3-r0 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →