LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44386: 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. SetPtzPatrol 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

A flaw in the Reolink RLC-410W camera's web CGI handling can let a remote attacker crash and reboot the device with a crafted HTTP request. The business risk is availability: cameras may go offline at important times. The source bundle identifies one firmware version and does not name a vendor fix.

Executive priority

Treat as high priority for surveillance or safety-sensitive sites because exploitation can take cameras offline. Prioritize exposed or unsegmented cameras first. The available sources do not provide confidentiality impact, data theft evidence, active exploitation, or a named patch.

Technical view

CVE-2021-44386 is CWE-20 improper input validation in cgiserver.cgi's JSON command parser on Reolink RLC-410W v3.0.0.136_20121102. The described trigger is a SetPtzPatrol parameter with an unexpected type, causing device reboot. CVSS 3.0 is 8.6, network-reachable, low complexity, unauthenticated, no user interaction, availability-only impact.

Likely exposure

Likely exposure is limited to reachable Reolink RLC-410W cameras running v3.0.0.136_20121102. The bundle's structured affected-product fields are incomplete, so do not assume other Reolink models or firmware versions are affected without vendor or Talos confirmation.

Exploitation context

The sources describe a crafted HTTP request causing reboot. CISA KEV status is false in the bundle, and no cited source here states active exploitation. The vulnerability is still operationally relevant where affected cameras are internet-exposed or reachable from untrusted networks.

Researcher notes

The source bundle names a single firmware version in the narrative but has incomplete structured affected fields. Analysis should stay scoped to Reolink RLC-410W v3.0.0.136_20121102 unless further vendor data expands coverage. Avoid assuming exploit-in-the-wild status because KEV is false and no source here supports it.

Mitigation direction

  • Identify Reolink RLC-410W devices and confirm firmware versions.
  • Check Reolink and Talos guidance for fixed firmware or official mitigations.
  • Remove camera management interfaces from internet exposure.
  • Restrict access to trusted administrative networks or VPNs.
  • Monitor for unexpected camera reboots or availability gaps.

Validation and detection

  • Inventory cameras by model, firmware, and management interface exposure.
  • Verify whether any RLC-410W devices run v3.0.0.136_20121102.
  • Review network paths to cgiserver.cgi from untrusted segments.
  • Check logs or monitoring for unexplained reboot patterns.
  • Document compensating controls if no vendor fix is available.
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-44386 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-44386Attack 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.