CVE-2023-26053
Assigner: GitHub_M
Published: 2023-03-02T03:11:31.488Z
State: PUBLISHED
title: Gradle usage of long IDs for PGP keys opens potential for collision attacks
problemTypes: descriptions: cweId: CWE-829
description: CWE-829: Inclusion of Functionality from Untrusted Control Sphere
type: CWE
metrics: cvssV3_1: attackComplexity: HIGH
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 6.6
baseSeverity: MEDIUM
confidentialityImpact: HIGH
integrityImpact: HIGH
privilegesRequired: HIGH
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
version: 3.1
affected: vendor: gradle
product: gradle
versions: version: >= 6.2, < 6.9.4
status: affected
version: >= 7.0.0, < 7.6.1
status: affected
descriptions: value: 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.
source: advisory: GHSA-c724-3xg7-g3hf
discovery: UNKNOWN