# CVE-2019-15595: Command injection in UniFi Video Server

> A local attacker can execute arbitrary commands on the UniFi Video Controller, leading to privilege escalation and full system compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8x5r-42wx-8grh

## What is CVE-2019-15595?

CVE-2019-15595 is a high-severity command injection vulnerability in UniFi Video Server, published on 25 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A privilege escalation exists in UniFi Video Controller =<3.10.6 that would allow an attacker on the local machine to run arbitrary commands.

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

## Which versions are affected by CVE-2019-15595?

It affects 1 product.


Products: Ui Unifi Video Controller.

## How do I fix CVE-2019-15595?

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

## Is CVE-2019-15595 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15595 and fix it if it is affected.

What it is: CVE-2019-15595 is a high-severity command injection vulnerability in UniFi Video Server, published on 25 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-15595 in the wild and no public exploit code.

Affected product: UniFi Video 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-2019-15595/ (Markdown: https://insights.sbomify.com/CVE-2019-15595/index.md)
```

## Sources

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

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