{"uuid": "47185e3f-58cf-4ae1-85f8-b8f9f335e694", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-25204", "type": "seen", "source": "https://t.me/cvedetector/18128", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-25204 - GitHub gh Artifact Attestation Verification Exit Code Spoofing Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-25204 \nPublished : Feb. 14, 2025, 5:15 p.m. | 1\u00a0hour, 2\u00a0minutes ago \nDescription : `gh` is GitHub\u2019s official command line tool. Starting in version 2.49.0 and prior to version 2.67.0, under certain conditions, a bug in GitHub's Artifact Attestation cli tool `gh attestation verify` causes it to return a zero exit status when no attestations are present. This behavior is incorrect: When no attestations are present, `gh attestation verify` should return a non-zero exit status code, thereby signaling verification failure. An attacker can abuse this flaw to, for example, deploy malicious artifacts in any system that uses `gh attestation verify`'s exit codes to gatekeep deployments. Users are advised to update `gh` to patched version `v2.67.0` as soon as possible. \nSeverity: 6.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"14 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-14T19:57:03.000000Z"}