Yubico OTP
Approved changes feed: RSS · Atom
cpe:2.3:a:yubico:otp:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Yubico (f47f12e0-b4db-5ed2-80cf-70347f747b11) |
|---|---|
| Product | Otp (5cac8d74-3e8e-5235-8be3-42cc1c1e6edb) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-24584 |
vulnerable | 2026-06-03 14:46:30.722157 |
Details available
Incorrect access control in Yubico OTP functionality of the YubiKey hardware tokens along with the Yubico OTP validation server. The Yubico OTP supposedly creates hardware bound second factor credentials. When a user reprograms the OTP functionality by "writing" it on a token using the Yubico Personalization Tool, they can then upload the new configuration to Yubicos OTP validation servers. NOTE: the vendor disputes this because there is no way for a YubiKey device to prevent a user from deciding that a secret value, which is imported into the device, should also be stored elsewhere
Published: 2022-05-11T17:49:59.000Z
Updated: 2024-08-03T04:13:56.866Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.