Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-11001: OS Command Injection in Reolink Camera TestEmail Functionality

Published Apr 8, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.2High · v3.1
EPSS37.5%99th percentile
CISA KEVYesAdded Dec 18, 2024
In the wildActivePer CISA KEV
Vendor
Reolink
IdentifiersCVE-2019-11001CWE-78 · Improper Neutralization of Special…

A vulnerability in Reolink RLC-410W, C1 Pro, C2 Pro, RLC-422W, and RLC-511W devices through firmware version 1.0.227 allows an authenticated administrator to execute arbitrary OS commands as root. The vulnerability exists in the 'TestEmail' functionality, where user-supplied input in the 'addr1' field is not properly sanitized, permitting shell metacharacter injection and subsequent command execution with root privileges.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote authenticated administrator to execute arbitrary commands as root on the affected device, leading to full device compromise, persistent access, and potential lateral movement within the network.

Mitigation

If you can’t patch tonight, do this now.

Restrict administrative access to trusted users and networks, monitor device logs for suspicious TestEmail activity, and consider network segmentation to limit exposure of vulnerable devices until patched.

Remediation

Patch, then assume compromise.

Upgrade the device firmware to a version that properly sanitizes user input in the TestEmail functionality, or apply any official patches provided by Reolink addressing this issue.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ReolinkC1-Pro Firmwareoperating_system
ReolinkC2 Pro Firmwareoperating_system
ReolinkRlc-410w Firmwareoperating_system
ReolinkRlc-422w Firmwareoperating_system
ReolinkRlc-511w Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2019-11001 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Dec 18, 2024.
Is there a public exploit for CVE-2019-11001?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2019-11001.
Is there a patch for CVE-2019-11001?
Upgrade the device firmware to a version that properly sanitizes user input in the TestEmail functionality, or apply any official patches provided by Reolink addressing this issue.
What products are affected by CVE-2019-11001?
Reolink C1-Pro Firmware, Reolink C2 Pro Firmware, Reolink Rlc-410w Firmware, Reolink Rlc-422w Firmware, and Reolink Rlc-511w Firmware.
How severe is CVE-2019-11001?
CVE-2019-11001 has a CVSS v3.1 score of 7.2 (High) and an EPSS score of 37.5% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.