CVE-2025-25204: `gh attestation verify` returns incorrect exit code during verification if no attestations are present
First published: Fri Feb 14 2025(Updated: )
### Summary A bug in GitHub's Artifact Attestation CLI tool, `gh attestation verify`, may return an incorrect zero exit status when no matching attestations are found for the specified `--predicate-type <value>` or the default `https://slsa.dev/provenance/v1` if not specified. This issue only arises if an artifact has an attestation with a predicate type different from the one provided in the command. As a result, users relying solely on these exit codes may mistakenly believe the attestation has been verified, despite the absence of an attestation with the specified predicate type and the tool printing a verification failure. Users are advised to update `gh` to version `v2.67.0` as soon as possible. Initial report: https://github.com/cli/cli/issues/10418 Fix: https://github.com/cli/cli/pull/10421 ### Details The gh attestation verify command fetches, loads, and attempts to verify attestations associated with a given artifact for a specified predicate type. If an attestation is found, but the predicate type does not match the one specified in the `gh attestation verify` command, the verification fails, but the program exits early. Due to a re-used uninitialized error variable, when no matching attestations are found, the relevant function returns `nil` instead of an error, causing the program to exit with a status code of `0`, which incorrectly suggests successful verification. ### PoC Run `gh attestation verify` with local attestations using the `--bundle` flag and specify a predicate type with `--predicate-type` that you know will not match any of the attestations the command will attempt to verify. Confirm that the command exits with a zero status code. ### Impact Users who rely exclusively on the exit status code of `gh attestation verify` may incorrectly verify an attestation when the attestation's predicate type does not match the specified predicate type in the command.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitHub | >2.49.0<=2.67.0 | |
| go/github.com/cli/cli/v2 | >=2.49.0<2.67.0 | 2.67.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-25204?
CVE-2025-25204 is considered a moderate severity vulnerability due to its potential to mislead users about the presence of attestations.
How do I fix CVE-2025-25204?
To fix CVE-2025-25204, upgrade the GitHub CLI tool `gh` to version 2.67.0 or later.
What versions of `gh` are affected by CVE-2025-25204?
CVE-2025-25204 affects versions of the GitHub CLI tool `gh` from 2.49.0 up to (but not including) 2.67.0.
What is the impact of CVE-2025-25204 on users?
The impact of CVE-2025-25204 on users is that it may lead to incorrect behavior where the tool reports success even when no attestations are present.
Is there a workaround for CVE-2025-25204?
There are no documented workarounds for CVE-2025-25204; the recommended action is to upgrade to a fixed version.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/type
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/softwarecombine
- agent/description
- collector/nvd-cve
- agent/references
- agent/event
- agent/source
- agent/tags
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-fgw4-v983-mgp8
- alias/CVE-2025-25204
- agent/last-modified-date
- collector/epss-latest
- source/FIRST
- collector/github-advisory
- agent/epss
- vendor/github
- canonical/github
- package-manager/go