LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44407: 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. TestEmail 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 flaw can let a remote attacker force a reboot of a specific Reolink camera model through its web CGI interface. The business impact is availability: affected cameras may stop monitoring or recording during disruption. The provided sources do not state data theft or device takeover.

Executive priority

Treat this as a high-priority availability risk for sites relying on the affected camera model for monitoring, safety, or evidence capture. Urgency rises sharply if management interfaces are internet-exposed or reachable from broad internal networks.

Technical view

CVE-2021-44407 is a CWE-20 input validation issue in the cgiserver.cgi JSON command parser of Reolink RLC-410W v3.0.0.136_20121102. A malformed TestEmail parameter that is not an object can trigger denial of service by rebooting the device. CVSS is 8.6, network exploitable, unauthenticated, no user interaction.

Likely exposure

Exposure is likely limited to Reolink RLC-410W devices running firmware v3.0.0.136_20121102 where the camera web interface or cgiserver.cgi is reachable from untrusted networks. The bundled affected-product metadata is incomplete, so confirm model and firmware through asset inventory.

Exploitation context

The bundle does not indicate CISA KEV listing or active exploitation. The CVE description says an attacker can trigger the issue with an HTTP request, but no public exploit status is established by the provided sources.

Researcher notes

The primary evidence identifies one model and firmware version, but the structured affected fields are n/a. Focus research on firmware confirmation, parser behavior around TestEmail, reboot observability, and whether later Reolink firmware addresses the flaw. Do not assume broader product impact without vendor evidence.

Mitigation direction

  • Identify any Reolink RLC-410W devices running firmware v3.0.0.136_20121102.
  • Restrict camera management interfaces to trusted administrative networks only.
  • Check Reolink and Talos guidance for vendor-confirmed firmware updates or workarounds.
  • Monitor affected cameras for unexpected reboots and loss of recording continuity.
  • Prioritize replacement or isolation if no vendor fix is available.

Validation and detection

  • Inventory camera model, firmware version, and network exposure.
  • Confirm whether cgiserver.cgi is reachable from untrusted segments.
  • Review device logs or monitoring for unexplained reboot events.
  • Check firewall, VPN, and access-control rules protecting camera management access.
  • Use only authorized lab validation; avoid production disruption testing.
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-44407 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-44407Attack 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.