LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44414: A denial of service vulnerability exists in the cgiserver.cgi JSON command parser functionality of reolink...

A denial of service vulnerability exists in the cgiserver.cgi JSON command parser functionality of reolink RLC-410W v3.0.0.136_20121102. A specially-crafted HTTP request can lead to a reboot. DelUser param is not object. An attacker can send an HTTP request to trigger this vulnerability.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue can let a remote attacker force a vulnerable Reolink RLC-410W camera to reboot by sending a crafted HTTP request. The business impact is service disruption: camera downtime, reduced monitoring coverage, and possible repeated outages if the device is reachable from untrusted networks.

Executive priority

Treat this as a high-priority availability risk for sites relying on affected cameras for monitoring or physical security. Prioritize exposed devices first, then internal devices in less trusted network zones.

Technical view

The vulnerability is improper input validation in the cgiserver.cgi JSON command parser. For Reolink RLC-410W firmware v3.0.0.136_20121102, a malformed DelUser parameter can trigger a reboot. The CVSS vector indicates unauthenticated, network-reachable, low-complexity denial of service with high availability impact.

Likely exposure

Exposure is most likely where the specific Reolink RLC-410W firmware is deployed and its HTTP management/API surface is reachable from the internet, guest networks, or other untrusted segments. The provided CVE metadata does not identify broader affected products.

Exploitation context

The source bundle describes attacker-triggered reboot through an HTTP request. It does not include CISA KEV listing or other evidence of active exploitation, so active exploitation should not be assumed from these sources.

Researcher notes

The CVE affected-product fields are not normalized, but the description names Reolink RLC-410W v3.0.0.136_20121102. Evidence is specific to denial of service and reboot behavior; no confidentiality or integrity impact is described in the supplied sources.

Mitigation direction

  • Inventory Reolink RLC-410W cameras and identify firmware v3.0.0.136_20121102.
  • Check Reolink or Talos guidance for fixed firmware or vendor-recommended mitigation.
  • Restrict camera HTTP management access to trusted administration networks only.
  • Remove internet exposure for affected camera interfaces where present.
  • Monitor affected devices for repeated unexplained reboots or availability drops.

Validation and detection

  • Confirm whether any deployed camera matches Reolink RLC-410W firmware v3.0.0.136_20121102.
  • Review firewall, VPN, and NAT rules for camera HTTP interface exposure.
  • Check uptime, device logs, and monitoring alerts for unexpected reboot patterns.
  • Verify vendor guidance before performing active vulnerability testing.
  • Document compensating controls if fixed firmware is unavailable or unconfirmed.
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-20: 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-44414 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
High
CVSS
8.6 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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
8.6CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H3.94Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.6High
CVSS 3.0 vector shape for CVE-2021-44414Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.