# CVE-2021-28811: Vulnerability in Roon Server

> Remote attackers can execute arbitrary commands on Roon Server, requiring an upgrade to the latest version for mitigation.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-67fr-wg95-6gwh

## What is CVE-2021-28811?

CVE-2021-28811 is a high-severity command injection vulnerability in Roon Server, published on 8 Jun 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

If exploited, this command injection vulnerability could allow remote attackers to run arbitrary commands. Roon Labs has already fixed this vulnerability in the following versions: Roon Server 2021-05-18 and later

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Roonlabs Roon Server.

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

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

## Is CVE-2021-28811 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-28811 is a high-severity command injection vulnerability in Roon Server, published on 8 Jun 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-28811 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-28811/ (Markdown: https://insights.sbomify.com/CVE-2021-28811/index.md)
```

## Sources

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

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