Bug 2239399 (CVE-2022-31156) - CVE-2022-31156 gradle: Dependency verification can ignore checksum verification when signature verification cannot be performed
Summary: CVE-2022-31156 gradle: Dependency verification can ignore checksum verificati...
Status: NEW
Alias: CVE-2022-31156
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Product Security
QA Contact:
Depends On: 2239400 2239401 2239402
Blocks: 2108076
TreeView+ depends on / blocked
Reported: 2023-09-18 07:16 UTC by Avinash Hanwate
Modified: 2023-09-30 15:40 UTC (History)
26 users (show)

Fixed In Version: Gradle 7.5
Doc Type: ---
Doc Text:
A flaw was found in Gradle, which allows a remote, authenticated attacker to bypass security restrictions caused by an issue of dependency verification. It can ignore checksum verification when signature verification cannot be performed. By sending a specially crafted request, an attacker can download the malicious binary from the arbitrary repository or perform a man-in-the-middle attack.
Clone Of:
Last Closed:

Attachments (Terms of Use)

Description Avinash Hanwate 2023-09-18 07:16:42 UTC
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. When signature verification is enabled, the verification metadata contains entries for dependencies with a `gpg` element but there is no signature file on the remote repository. In both cases, the verification will accept the dependency, skipping signature verification and not complaining that the dependency has no checksum entry. For builds that are vulnerable, there are two risks. Gradle could download a malicious binary from a repository outside your organization due to name squatting. For those still using HTTP only and not HTTPS for downloading dependencies, the build could download a malicious library instead of the expected one. Gradle 7.5 patches this issue by making sure to run checksum verification if signature verification cannot be completed, whatever the reason. Two workarounds are available: Remove all `gpg` elements from dependency verification metadata if you disable signature validation and/or avoid adding `gpg` entries for dependencies that do not have signature files.


Comment 1 Avinash Hanwate 2023-09-18 07:19:39 UTC
Created picocli tracking bugs for this issue:

Affects: fedora-38 [bug 2239401]

Note You need to log in before you can comment on or make changes to this bug.