LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44399: 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. GetPtzPreset 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 interruption: cameras may be unavailable during incidents or monitoring windows. The provided sources do not show data theft or device takeover.

Executive priority

Prioritize if these cameras protect safety, physical security, or regulated facilities. The issue is availability-focused, but camera outages during an incident can create business and operational risk. Internet-exposed devices should be addressed first.

Technical view

CVE-2021-44399 is a CWE-20 input validation flaw in the cgiserver.cgi JSON command parser. Sources describe Reolink RLC-410W v3.0.0.136_20121102, where an invalid GetPtzPreset parameter can trigger a device reboot. CVSS is 8.6 because the attack is network reachable, unauthenticated, low complexity, and availability-impacting.

Likely exposure

Exposure appears limited to Reolink RLC-410W devices running firmware v3.0.0.136_20121102, based on the source description. Broader affected versions or products are not established in the provided evidence. Internet-facing camera management endpoints would materially increase risk.

Exploitation context

The sources say an attacker can send an HTTP request to trigger the reboot. CISA KEV is false in the bundle, and no provided source confirms active exploitation. Treat exploitation status as unconfirmed, not absent.

Researcher notes

The provided evidence is narrow: one named model and firmware, unauthenticated network reachability, and reboot impact. No patch details, exploit-in-the-wild confirmation, or expanded affected-version list are included. Avoid assuming other Reolink models are affected without vendor evidence.

Mitigation direction

  • Check Reolink and Talos guidance for corrected firmware or vendor-recommended mitigation.
  • Remove camera management interfaces from direct Internet exposure.
  • Restrict HTTP access to trusted administration networks or VPN paths.
  • Monitor vulnerable cameras for unexplained reboots or availability loss.
  • Prioritize replacement or isolation where no vendor fix is available.

Validation and detection

  • Inventory Reolink RLC-410W devices and record firmware versions.
  • Identify any devices running v3.0.0.136_20121102.
  • Confirm camera HTTP management endpoints are not publicly reachable.
  • Review monitoring and logs for repeated unexpected reboots.
  • Track vendor advisories for patch availability or clarified affected versions.
Prepared
Confidence
high
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-44399 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-44399Attack 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.