{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-29991 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-29991 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-29991 is a low-severity vulnerability in Yubico YubiKey, published on 3 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-29991 and fix it if it is affected.\n\nWhat it is: CVE-2025-29991 is a low-severity vulnerability in Yubico YubiKey, published on 3 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-29991 in the wild and no public exploit code.\n\nAffected product: Yubico YubiKey. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-29991/ (Markdown: https://insights.sbomify.com/CVE-2025-29991/index.md)","id":"CVE-2025-29991","markdown":"https://insights.sbomify.com/CVE-2025-29991/index.md","name":"CVE-2025-29991","record":{"aliases":["GHSA-2rq3-x44v-xx2w"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"YubiKey hardware token","requires_auth":"low_privilege","summary":"Attackers can bypass PIN/UV authentication checks on YubiKey devices due to incorrect signature length verification in Protocol Two.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1390","name":"Weak Authentication"}],"description":"Yubico YubiKey 5.4.1 through 5.7.3 before 5.7.4 has an incorrect FIDO CTAP PIN/UV Auth Protocol Two implementation. It uses the signature length from CTAP PIN/UV Auth Protocol One, even when CTAP PIN/UV Auth Protocol Two was chosen, resulting in a partial signature verification.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in YubiKey","id":"CVE-2025-29991","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-29992"},"packages":[],"prev":{"headline":"Security feature bypass in Dell Client Platform BIOS","id":"CVE-2025-29989"},"products":["YubiKey"],"published":"2025-04-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-03","vendors":["Yubico"]},"summary":"Attackers can bypass PIN/UV authentication checks on YubiKey devices due to incorrect signature length verification in Protocol Two.","url":"https://insights.sbomify.com/CVE-2025-29991/"}