LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44402: 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. GetPtzSerial 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

CVE-2021-44402 can let an unauthenticated network attacker crash and reboot a vulnerable Reolink camera with a crafted HTTP request. The business impact is loss of camera availability, which matters most where cameras support physical security, monitoring, or incident response.

Executive priority

Treat this as high priority for exposed or operationally important cameras. It is not a data-theft issue in the provided evidence, but forced reboots can blind monitoring coverage and weaken physical security reliability.

Technical view

The flaw is improper input validation in the cgiserver.cgi JSON command parser for Reolink RLC-410W v3.0.0.136_20121102. The source description identifies the GetPtzSerial parameter being supplied in an unexpected type, causing a reboot. CVSS is 8.6 with network attack vector, low complexity, no privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is most likely where Reolink RLC-410W cameras on the cited firmware expose their HTTP CGI interface to untrusted networks. The structured affected-product metadata is incomplete, so validate against device model, firmware, and vendor advisory data.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation evidence. Talos reported that an attacker can send an HTTP request to trigger the reboot, but this analysis does not provide exploit steps or payload details.

Researcher notes

CWE-20 aligns with the described parser type-validation failure. The CVE record’s structured affected list is not populated, while the description names Reolink RLC-410W v3.0.0.136_20121102. No patch, workaround, or active exploitation claim is included in the supplied evidence.

Mitigation direction

  • Check Reolink and Talos guidance for fixed firmware or vendor-recommended workarounds.
  • Remove camera HTTP management interfaces from public internet exposure.
  • Restrict access to trusted admin networks or VPN paths only.
  • Segment security cameras from general user and guest networks.
  • Prioritize remediation where camera downtime affects physical security operations.

Validation and detection

  • Inventory Reolink RLC-410W devices and record firmware versions.
  • Identify any devices running v3.0.0.136_20121102.
  • Confirm whether cgiserver.cgi or camera HTTP management is reachable from untrusted networks.
  • Review monitoring for unexpected camera reboots or availability drops.
  • Track vendor advisory status because source metadata does not name a patch.
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-44402 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-44402Attack 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.