CVSS: 7.6EPSS: 0%CPEs: 1EXPL: 0CVE-2023-30853 – Gradle Build Action data written to GitHub Actions Cache may expose secrets
https://notcve.org/view.php?id=CVE-2023-30853
Gradle Build Action allows users to execute a Gradle Build in their GitHub Actions workflow. A vulnerability impacts GitHub workflows using the Gradle Build Action prior to version 2.4.2 that have executed the Gradle Build Tool with the configuration cache enabled, potentially exposing secrets configured for the repository. Secrets configured for GitHub Actions are normally passed to the Gradle Build Tool via environment variables. Due to the way that the Gradle Build Tool records these environment variables, they may be persisted into an entry in the GitHub Actions cache. This data stored in the GitHub Actions cache can be read by a GitHub Actions workflow running in an untrusted context, such as that running for a Pull Request submitted by a developer via a repository fork. This vulnerability was discovered internally through code review, and we have not seen any evidence of it being exploited in the wild. However, in addition to upgrading the Gradle Build Action, affected users should delete any potentially vulnerable cache entries and may choose to rotate any potentially affected secrets. Gradle Build Action v2.4.2 and newer no longer saves this sensitive data for later use, preventing ongoing leakage of secrets via the GitHub Actions Cache. While upgrading to the latest version of the Gradle Build Action will prevent leakage of secrets going forward, additional actions may be required due to current or previous GitHub Actions Cache entries containing this information. Current cache entries will remain vulnerable until they are forcibly deleted or they expire naturally after 7 days of not being used. • https://github.com/gradle/gradle-build-action/releases/tag/v2.4.2 https://github.com/gradle/gradle-build-action/security/advisories/GHSA-h3qr-39j9-4r5v • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor CWE-312: Cleartext Storage of Sensitive Information •
CVSS: 9.8EPSS: 0%CPEs: 2EXPL: 0CVE-2023-26053 – Gradle usage of long IDs for PGP keys opens potential for collision attacks
https://notcve.org/view.php?id=CVE-2023-26053
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. • https://github.com/gradle/gradle/commit/bf3cc0f2b463033037e67aaacda31291643ea1a9 https://github.com/gradle/gradle/security/advisories/GHSA-c724-3xg7-g3hf https://security.netapp.com/advisory/ntap-20230413-0002 • CWE-829: Inclusion of Functionality from Untrusted Control Sphere •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-41575
https://notcve.org/view.php?id=CVE-2022-41575
A credential-exposure vulnerability in the support-bundle mechanism in Gradle Enterprise 2022.3 through 2022.3.3 allows remote attackers to access a subset of application data (e.g., cleartext credentials). This is fixed in 2022.3.3. Una vulnerabilidad de exposición de credenciales en el mecanismo de support-bundle en Gradle Enterprise versiones 2022.3 hasta 2022.3.3, permite a atacantes remotos acceder a un subconjunto de datos de la aplicación (por ejemplo, credenciales en texto sin cifrar). Esto ha sido corregido en versión 2022.3.3 • https://security.gradle.com https://security.gradle.com/advisory/2022-13 • CWE-522: Insufficiently Protected Credentials •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0CVE-2022-41574
https://notcve.org/view.php?id=CVE-2022-41574
An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to prevent backups from occurring, and send emails with arbitrary text content to the configured installation-administrator contact address, via HTTP access to an accidentally exposed internal endpoint. This is fixed in 2022.3.2. Una vulnerabilidad de control de acceso en Gradle Enterprise versiones 2022.4 hasta 2022.3.1 permite a atacantes remotos evitar que sean realizadas copias de seguridad y enviar correos electrónicos con contenido de texto arbitrario a la dirección de contacto del administrador de la instalación configurada, por medio de acceso HTTP a un endpoint interno expuesto accidentalmente. Esto ha sido corregido en versión 2022.3.2 • https://security.gradle.com https://security.gradle.com/advisory/2022-12 • CWE-863: Incorrect Authorization •
CVSS: 6.6EPSS: 0%CPEs: 1EXPL: 0CVE-2022-31156 – Gradle's dependency verification can ignore checksum verification when signature verification cannot be performed
https://notcve.org/view.php?id=CVE-2022-31156
Gradle is a build tool. Dependency verification is a security feature in Gradle Build Tool that was introduced to allow validation of external dependencies either through their checksum or cryptographic signatures. In versions 6.2 through 7.4.2, there are some cases in which Gradle may skip that verification and accept a dependency that would otherwise fail the build as an untrusted external artifact. This can occur in two ways. When signature verification is disabled but the verification metadata contains entries for dependencies that only have a `gpg` element but no `checksum` element. • https://docs.gradle.org/7.5/release-notes.html https://github.com/gradle/gradle/security/advisories/GHSA-j6wc-xfg8-jx2j • CWE-347: Improper Verification of Cryptographic Signature CWE-829: Inclusion of Functionality from Untrusted Control Sphere •