CVE-2019-11001
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.
do firstThe impacted product could be end-of-life (EoL) and/or end-of-service (EoS). Users should discontinue product utilization if a current mitigation is unavailable.
Can a WAF block it? No. The attack requires an authenticated admin user to send a request using the 'TestEmail' functionality with shell metacharacters in the addr1 field. Since the request looks like a normal admin action and requires valid credentials, a WAF cannot reliably distinguish malicious input from legitimate use.
Also consider: shlex/execve-style APIs
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2019-11001 being exploited?
Yes. CVE-2019-11001 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2019-11001?
CVE-2019-11001 is rated High with a CVSS score of 7.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2019-11001?
Not known from our data. No patch reference has been recorded for CVE-2019-11001, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2019-11001 affect?
CVE-2019-11001 affects reolink:rlc-410w_firmware, reolink:c1_pro_firmware, reolink:c2_pro_firmware, reolink:rlc-422w_firmware, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 21 Dec 2024 (SSVC 2.0.3).
timeline
- 8 Apr 2019Published
- 18 Dec 2024Added to CISA KEV (exploited in the wild) · 2,080 days (about 6 years) later
- 21 Dec 2024CISA SSVC assessment: exploitation active · 3 days later
- 8 Jan 2025CISA remediation due date (US federal agencies) · 18 days later
- 21 Oct 2025CVE record last updated · 287 days (about 10 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkvdoo.com /blog/working-with-the-community-%E2%80%93-significant-vulnerabilities-in-reolin
- Linkgithub.com /mcw0/PoC/blob/master/Reolink-IPC-RCE.py
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-11001
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.