SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2019-11001Public Intelligence Dossier
Source: reolink · Limited verification•Last verified: •Collection Degraded
CVE-2019-11001ListedHIGH (raw)CVSS 9.0CWE-78

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.

Published: 08 Apr 2019•Last updated: 17 Jun 2026, 07:42 AM IST•Source identifier: cve@mitre.org
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added18 Dec 2024
Due08 Jan 2025
RansomwareUnknown
CVSS score
9.0HIGH (raw)
AV:N/AC:L/Au:S/C:C/I:C/A:C
Metric sourcenvd@nist.gov
EPSS probability
37.5%0.375
Percentile99th
Weakness type
CWE-78
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; HIGH severity; Known exploitation signal from CISA KEV or ransomware metadata; Source-confirmed exploitation or CISA KEV/ransomware metadata

Affected Products & Remediation

5 source-backed products
Affected products and versions (source)
  • reolink rlc-410w firmware · <= 1.0.227 · NVD CPE · Source
  • reolink c1 pro firmware · <= 1.0.227 · NVD CPE · Source
  • reolink c2 pro firmware · <= 1.0.227 · NVD CPE · Source
  • reolink rlc-422w firmware · <= 1.0.227 · NVD CPE · Source
  • reolink rlc-511w firmware · <= 1.0.227 · NVD CPE · Source
NVD applicability prerequisites: cpe:2.3:h:reolink:rlc-410w:-:*:*:*:*:*:*:*, cpe:2.3:h:reolink:c1_pro:-:*:*:*:*:*:*:*, cpe:2.3:h:reolink:c2_pro:-:*:*:*:*:*:*:*, cpe:2.3:h:reolink:rlc-422w:-:*:*:*:*:*:*:*, cpe:2.3:h:reolink:rlc-511w:-:*:*:*:*:*:*:*. These are conditions, not proof that an environment is exposed or unaffected.
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: The 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.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: The 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.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); command-injection (CWE-78)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Identify installations of the affected product and compare versions with the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · A weakness class does not establish local exposure. · Rule command-injection

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review command interpreters spawned by the affected service or application.Telemetry: DeviceProcessEvents · Unexpected process lineage can support command-injection hunting. · Rule command-injection

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
18 Dec 2024
Required action due
08 Jan 2025
Known ransomware use
Unknown

The 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.

Change History & Source Data

— No recorded material change

CNA / source
cve@mitre.org
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:o:reolink:rlc-410w_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:reolink:rlc-410w:-:*:*:*:*:*:*:*, cpe:2.3:o:reolink:c1_pro_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:reolink:c1_pro:-:*:*:*:*:*:*:*, cpe:2.3:o:reolink:c2_pro_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:reolink:c2_pro:-:*:*:*:*:*:*:*, cpe:2.3:o:reolink:rlc-422w_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:reolink:rlc-422w:-:*:*:*:*:*:*:*, cpe:2.3:o:reolink:rlc-511w_firmware:*:*:*:*:*:*:*:*, cpe:2.3:h:reolink:rlc-511w:-:*:*:*:*:*:*:*

Evidence & Provenance

4 public sources
CISA KEV CatalogAdded 2024-12-18nvd.nist.govSource recordgithub.comSource recordvdoo.comSource record

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2019-11001
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2019-11001
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2019-11001"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Open KQL Library

Looking up related community queries…

Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.