Reduced FIDO command integrity via truncated signature verification
Published Apr 3, 2025 · Updated Apr 3, 2025
Weak authentication in Yubico YubiKey 5.4.1 through 5.7.3 allows local users to submit partially verified FIDO commands. The PIN/UV Auth Protocol Two verifier checks only the first 16 bytes of the required 32-byte HMAC-SHA-256 signature, reusing Protocol One length. Exploitation requires local access, low privileges, and user interaction; retained protocol protections make exploitation difficult and bound the consequence to reduced command integrity.
Summary
What happened
Weak authentication in Yubico YubiKey 5.4.1 through 5.7.3 allows local users to submit partially verified FIDO commands. The PIN/UV Auth Protocol Two verifier checks only the first 16 bytes of the required 32-byte HMAC-SHA-256 signature, reusing Protocol One length. Exploitation requires local access, low privileges, and user interaction; retained protocol protections make exploitation difficult and bound the consequence to reduced command integrity.
The record
- CVE
- CVE-2025-29991
- Published
- Apr 3, 2025
- Updated
- Apr 3, 2025
- Vendor
- Yubico
- Product
- YubiKey
- Classifications
- CWE-1390
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Apr 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.4.1 <5.7.4
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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