# CVE-2019-11001: Reolink Multiple IP Cameras OS Command Injection

> An authenticated admin can inject OS commands via the TestEmail feature to execute arbitrary code as root on Reolink cameras.

- **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:** Yes, since 18 Dec 2024 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-73c7-5g37-cmq7

## What is CVE-2019-11001?

CVE-2019-11001 is a high-severity command injection vulnerability in Reolink Rlc-410w Firmware, published on 8 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

On Reolink RLC-410W, C1 Pro, C2 Pro, RLC-422W, and RLC-511W devices through 1.0.227, an authenticated admin can use the "TestEmail" functionality to inject and run OS commands as root, as demonstrated by shell metacharacters in the addr1 field.

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

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

It affects 5 products.


Products: Reolink C1 Pro Firmware, Reolink C2 Pro Firmware, Reolink Rlc-410w Firmware, Reolink Rlc-422w Firmware, Reolink Rlc-511w Firmware.

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

No fix has been published for CVE-2019-11001 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 8 Jan 2025.

## Is CVE-2019-11001 being exploited?

Yes. Attackers have exploited CVE-2019-11001 in the wild since at least 18 Dec 2024.

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11001 is a high-severity command injection vulnerability in Reolink Rlc-410w Firmware, published on 8 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-11001 in the wild since at least 18 Dec 2024.

Affected product: Reolink Rlc-410w Firmware. 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-11001/ (Markdown: https://insights.sbomify.com/CVE-2019-11001/index.md)
```

## Sources

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

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