LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44417: 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. GetAlarm 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 CVE can let an unauthenticated network attacker reboot a specific Reolink camera by sending a malformed HTTP request. The business impact is service disruption: surveillance coverage may drop until the device restarts. The sources do not show data theft, device takeover, or active exploitation.

Executive priority

Treat this as a high-priority availability risk for sites that rely on affected cameras for security monitoring. Prioritize externally reachable devices first, then cameras on shared internal networks. If the model or firmware is absent, urgency drops substantially.

Technical view

CVE-2021-44417 is a CWE-20 input validation flaw in the cgiserver.cgi JSON command parser for Reolink RLC-410W v3.0.0.136_20121102. A GetAlarm parameter that is not an object can trigger denial of service through reboot. CVSS is 8.6, network-reachable, low complexity, no privileges or user interaction, availability impact only.

Likely exposure

Exposure is most likely where Reolink RLC-410W cameras running v3.0.0.136_20121102 have their HTTP interface reachable from untrusted networks. Internet-facing cameras and flat IoT networks are higher risk. The bundle does not establish other affected models or versions.

Exploitation context

The CVE is not marked in KEV, and the provided sources do not state active exploitation. The described attack requires network access to the camera HTTP service and can cause reboot-based denial of service. No evidence in the bundle supports confidentiality or integrity compromise.

Researcher notes

The source bundle identifies one tested product and firmware version despite the affected metadata listing n/a. Do not broaden scope without vendor evidence. The vulnerability is input-validation related and availability-focused; remediation details are not named in the provided sources.

Mitigation direction

  • Check Reolink and Talos guidance for fixed firmware or vendor mitigations.
  • Remove camera HTTP management interfaces from internet exposure.
  • Restrict camera access with firewall rules, VPN, or isolated management networks.
  • Segment cameras from business-critical systems and user workstations.
  • Monitor affected cameras for repeated unexpected reboots or outages.

Validation and detection

  • Inventory Reolink RLC-410W devices and record firmware versions.
  • Confirm whether v3.0.0.136_20121102 is present in the environment.
  • Verify camera HTTP interfaces are not reachable from untrusted networks.
  • Review uptime, device logs, and monitoring for unexplained reboot patterns.
  • Document compensating controls where firmware fixes are unavailable.
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-44417 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-44417Attack 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.