First published: Thu Jul 09 2020(Updated: )
An issue was discovered in Yubico libykpiv before 2.1.0. lib/util.c in this library (which is included in yubico-piv-tool) does not properly check embedded length fields during device communication. A malicious PIV token can misreport the returned length fields during RSA key generation. This will cause stack memory to be copied into heap allocated memory that gets returned to the caller. The leaked memory could include PINs, passwords, key material, and other sensitive information depending on the integration. During further processing by the caller, this information could leak across trust boundaries. Note that RSA key generation is triggered by the host and cannot directly be triggered by the token.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Yubico libykpiv | <2.1.0 | |
Yubico Piv Tool Manager | <2.0.0 | |
Yubico Yubikey Smart Card Minidriver | <=4.1.0.172 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-13131 is a vulnerability in Yubico libykpiv before version 2.1.0 that allows a malicious PIV token to misreport the returned length fields during RSA key generation.
CVE-2020-13131 has a severity score of 4.3, which is considered medium.
Yubico libykpiv before version 2.1.0, Yubico Piv Tool Manager before version 2.0.0, and Yubico Yubikey Smart Card Minidriver before version 4.1.0.172 are affected.
A malicious PIV token can exploit CVE-2020-13131 by misreporting the returned length fields during RSA key generation.
Yes, you can find more information about CVE-2020-13131 at the following links: [Link 1](https://blog.inhq.net/posts/yubico-libykpiv-vuln/) and [Link 2](https://www.yubico.com/products/services-software/download/smart-card-drivers-tools/).