LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40419: A firmware update vulnerability exists in the 'factory' binary of reolink RLC-410W v3.0.0.136_20121102.

A firmware update vulnerability exists in the 'factory' binary of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted series of network requests can lead to arbitrary firmware update. An attacker can send a sequence of requests to trigger this vulnerability.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This flaw could let an unauthenticated network attacker force an affected Reolink RLC-410W camera to accept an arbitrary firmware update. For executives, treat exposed cameras as high-risk because firmware control can undermine confidentiality, integrity, and availability.

Executive priority

Prioritize exposed or business-critical cameras first. A firmware update flaw can give an attacker durable control of a device, so remediation should be handled as an urgent infrastructure risk, not routine camera maintenance.

Technical view

CVE-2021-40419 affects the 'factory' binary in Reolink RLC-410W firmware v3.0.0.136_20121102. The CVSS 10.0 vector is network reachable, low complexity, no privileges, no user interaction, scope changed, and high impact to confidentiality, integrity, and availability.

Likely exposure

Exposure is most likely where Reolink RLC-410W cameras running v3.0.0.136_20121102 are reachable over untrusted networks. The provided affected metadata is incomplete, so validate by model and firmware version rather than relying on CPE matching.

Exploitation context

The source states a specially crafted series of network requests can trigger arbitrary firmware update. No provided source says this is in CISA KEV or actively exploited in the wild.

Researcher notes

The bundle names Reolink RLC-410W v3.0.0.136_20121102 and CWE-489, but affected product metadata is listed as n/a. Confidence is limited by sparse patch and mitigation details in the provided sources.

Mitigation direction

  • Identify affected Reolink RLC-410W cameras and confirm exact firmware version.
  • Check Reolink and Talos guidance for fixed firmware or vendor-approved remediation.
  • Remove camera management and update services from internet exposure.
  • Restrict access with network segmentation, firewall rules, and trusted administrative networks.
  • Monitor for unexpected firmware update activity or configuration changes.

Validation and detection

  • Inventory camera models and firmware versions across all sites.
  • Confirm whether any affected cameras are reachable from untrusted networks.
  • Review device logs or management records for unexpected firmware update events.
  • Check asset scanners for Reolink RLC-410W and firmware v3.0.0.136_20121102.
  • Track vendor advisory status before declaring remediation complete.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-489: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-40419 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.0CriticalCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

10Critical
CVSS 3.0 vector shape for CVE-2021-40419Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-489 · source CWE mapping

Active Debug Code

Active Debug Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.