Yubico YubiKey up to 5.2.6/5.3.1 OTP Application information disclosure

Summaryinfo

A vulnerability identified as problematic has been detected in Yubico YubiKey up to 5.2.6/5.3.1. Affected by this vulnerability is an unknown functionality of the component OTP Application. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2020-15001. The attack can only be initiated within the local network. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Yubico YubiKey up to 5.2.6/5.3.1. This issue affects some unknown functionality of the component OTP Application. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

An information leak was discovered on Yubico YubiKey 5 NFC devices 5.0.0 to 5.2.6 and 5.3.0 to 5.3.1. The OTP application allows a user to set optional access codes on OTP slots. This access code is intended to prevent unauthorized changes to OTP configurations. The access code is not checked when updating NFC specific components of the OTP configurations. This may allow an attacker to access configured OTPs and passwords stored in slots that were not configured by the user to be read over NFC, despite a user having set an access code. (Users who have not set an access code, or who have not configured the OTP slots, are not impacted by this issue.)

The weakness was disclosed 07/09/2020 (Website). The advisory is shared at yubico.com. The identification of this vulnerability is CVE-2020-15001 since 06/23/2020. The attack can only be initiated within the local network. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entry VDB-157816 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Yubico

Name

• YubiKey

Version

• 5.2.0
• 5.2.1
• 5.2.2
• 5.2.3
• 5.2.4
• 5.2.5
• 5.2.6
• 5.3.0
• 5.3.1

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion