# CVE-2021-28810: Vulnerability in Roon Server

> An authentication bypass in Roon Server allows attackers to access protected resources without proper credentials, requiring an upgrade to the latest version.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-9f4w-c8mj-53r3

## What is CVE-2021-28810?

CVE-2021-28810 is a high-severity authentication bypass vulnerability in Roon Server, published on 8 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

If exploited, this vulnerability allows an attacker to access resources which are not otherwise accessible without proper authentication. Roon Labs has already fixed this vulnerability in the following versions: Roon Server 2021-05-18 and later

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2021-28810?

It affects 1 product.


Products: Qnap Roon Server.

## How do I fix CVE-2021-28810?

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

## Is CVE-2021-28810 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-28810 and fix it if it is affected.

What it is: CVE-2021-28810 is a high-severity authentication bypass vulnerability in Roon Server, published on 8 Jun 2021. 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-2021-28810 in the wild and no public exploit code.

Affected product: Roon Server. 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-2021-28810/ (Markdown: https://insights.sbomify.com/CVE-2021-28810/index.md)
```

## Sources

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

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