Artifact verification bypass via uninitialized error return
Published Feb 14, 2025 · Updated Mar 3, 2025
Improper error handling in GitHub CLI 2.49.0 through 2.66.1 allows remote authenticated users to bypass artifact verification. When no attestation matches the requested predicate type, the verification function returns a reused, uninitialized nil error, producing exit status 0. Exploitation requires an artifact with a different attestation predicate and a deployment gate that trusts only the command's exit status; the failure can admit a malicious artifact.
Summary
What happened
Improper error handling in GitHub CLI 2.49.0 through 2.66.1 allows remote authenticated users to bypass artifact verification. When no attestation matches the requested predicate type, the verification function returns a reused, uninitialized nil error, producing exit status 0. Exploitation requires an artifact with a different attestation predicate and a deployment gate that trusts only the command's exit status; the failure can admit a malicious artifact.
The record
- CVE
- CVE-2025-25204
- Published
- Feb 14, 2025
- Updated
- Mar 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-390, T1195
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 14, 2025CVE publishedPublication date reported by the CVE source.
- Mar 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Predicate-type mismatch exit-status proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo