Yubico libykpiv up to 2.0.x RSA Key Generation lib/util.c Length Field information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Yubico libykpiv up to 2.0.x. This vulnerability affects unknown code in the library lib/util.c of the component RSA Key Generation. Performing a manipulation as part of Length Field results in information disclosure. This vulnerability is cataloged as CVE-2020-13131. The attack may be carried out on the physical device. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Yubico libykpiv up to 2.0.x. This affects an unknown functionality in the library lib/util.c of the component RSA Key Generation. The manipulation as part of a Length Field leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
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.
The weakness was shared 07/09/2020 (Website). The advisory is shared at yubico.com. This vulnerability is uniquely identified as CVE-2020-13131 since 05/18/2020. An attack has to be approached locally. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 2.1.0 eliminates this vulnerability.
The entry VDB-157810 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.2VulDB Meta Temp Score: 3.1
VulDB Base Score: 2.1
VulDB Temp Score: 2.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libykpiv 2.1.0
Timeline
05/18/2020 🔍07/09/2020 🔍
07/10/2020 🔍
10/29/2020 🔍
Sources
Advisory: yubico.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-13131 (🔍)
GCVE (CVE): GCVE-0-2020-13131
GCVE (VulDB): GCVE-100-157809
See also: 🔍
Entry
Created: 07/10/2020 08:46Updated: 10/29/2020 09:59
Changes: 07/10/2020 08:46 (42), 07/10/2020 08:51 (11), 10/29/2020 09:53 (1), 10/29/2020 09:59 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.