# CVE-2020-10184: SQL injection in n/a

> Remote attackers can cause denial of service in self-hosted YubiKey Validation Servers via SQL injection in the verify endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4v4f-2vvr-7hf5, UBUNTU-CVE-2020-10184

## What is CVE-2020-10184?

CVE-2020-10184 is a high-severity SQL injection vulnerability in n/a, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The verify endpoint in YubiKey Validation Server before 2.40 does not check the length of SQL queries, which allows remote attackers to cause a denial of service, aka SQL injection. NOTE: this issue is potentially relevant to persons outside Yubico who operate a self-hosted OTP validation service; the issue does NOT affect YubiCloud.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-10184?

It affects 1 product.


Products: Yubico Yubikey One Time Password Validation Server.

## How do I fix CVE-2020-10184?

Upgrade to a fixed version.

## Is CVE-2020-10184 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-10185](https://insights.sbomify.com/CVE-2020-10185/): Business logic in n/a (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10184 and fix it if it is affected.

What it is: CVE-2020-10184 is a high-severity SQL injection vulnerability in n/a, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10184 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-2020-10184/ (Markdown: https://insights.sbomify.com/CVE-2020-10184/index.md)
```

## Sources

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

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