# CVE-2022-24584: Missing authorization in n/a

> Users can upload OTP configurations to validation servers, potentially bypassing hardware-bound second factor assumptions, though the vendor disputes this as intended behavior.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gwr3-p8fv-j5fg

## What is CVE-2022-24584?

CVE-2022-24584 is a medium-severity missing authorization vulnerability in n/a, published on 11 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2022-24584?

It affects 1 product.


Products: Yubico Otp.

## How do I fix CVE-2022-24584?

No fix has been published for CVE-2022-24584 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-24584 being exploited?

There is no known exploitation of CVE-2022-24584 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24584 and fix it if it is affected.

What it is: CVE-2022-24584 is a medium-severity missing authorization vulnerability in n/a, published on 11 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24584 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24584/ (Markdown: https://insights.sbomify.com/CVE-2022-24584/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24584
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24584
- OSV: https://osv.dev/vulnerability/CVE-2022-24584

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24584/
Summaries are generated and may contain mistakes; the official description above is the record.