CVE-2023-26053mediumCWE-829

CVE-2023-26053: medium-severity vulnerability in gradle

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

Published · Updated

Follow this CVE+ Monitor gradle+ Monitor gradle

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 6.6epss 1.0%
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` element in the metadata is a protection against this issue.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Affected products
gradle · gradle
Related CVEs — gradle

In the same product, most dangerous first.

CVE-2021-32751HIGHArbitrary code execution via specially crafted environment variablesEPSS 2.7%CVE-2022-23630HIGHDependency verification bypass in GradleEPSS 1.3%CVE-2021-29427HIGHRepository content filters do not work in Settings pluginManagementEPSS 1.3%CVE-2023-42445MEDIUMPossible local file exfiltration by XML External entity injectionEPSS 0.8%CVE-2022-31156MEDIUMGradle's dependency verification can ignore checksum verification when signature verification cannot be performedEPSS 0.6%CVE-2021-29428HIGHLocal privilege escalation through system temporary directoryEPSS 0.5%