LiveActive security incident?Get immediate response
CVE Record

CVE-2021-44355: Multiple denial of service vulnerabilities exist in the cgiserver.cgi JSON command parser functionality of...

Multiple denial of service vulnerabilities exist 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. 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 an unauthenticated network attacker reboot an affected Reolink RLC-410W camera by sending a crafted HTTP request. The business impact is availability loss: cameras may go offline or repeatedly restart, affecting monitoring and physical security coverage. The sources do not indicate data theft or camera takeover.

Executive priority

Prioritize remediation where affected cameras support perimeter, safety, or business-critical surveillance, or where their HTTP interface is exposed beyond trusted networks. The impact is operational disruption rather than confirmed confidentiality loss.

Technical view

CVE-2021-44355 covers multiple denial of service issues in the cgiserver.cgi JSON command parser of Reolink RLC-410W firmware v3.0.0.136_20121102. The CVSS 3.0 score is 8.6, with network access, low complexity, no privileges, no user interaction, changed scope, and high availability impact.

Likely exposure

Exposure is limited to Reolink RLC-410W devices running v3.0.0.136_20121102, especially where the camera HTTP interface is reachable from untrusted networks. The provided sources do not identify other Reolink models or firmware versions as affected.

Exploitation context

The sources state that an attacker can send a specially crafted HTTP request to trigger a reboot. The provided data does not list this CVE as KEV and does not provide evidence of active exploitation. Treat internet-reachable devices as higher risk because exploitation requires no credentials.

Researcher notes

The evidence is specific but narrow: affected product, firmware, parser component, HTTP trigger, reboot outcome, CWE-20, and CVSS vector are documented. The supplied sources do not name a fixed version, broader affected range, or confirmed in-the-wild exploitation.

Mitigation direction

  • Identify Reolink RLC-410W cameras and confirm firmware versions.
  • Check Reolink and Talos guidance for vendor-approved updates or mitigations.
  • Remove camera HTTP interfaces from direct internet exposure.
  • Restrict access using VPNs, firewalls, or management VLANs.
  • Monitor affected cameras for unexpected reboots or availability loss.

Validation and detection

  • Inventory camera model and firmware against v3.0.0.136_20121102.
  • Confirm whether the HTTP management interface is reachable from untrusted networks.
  • Review uptime, device logs, and monitoring for unexplained reboot patterns.
  • Verify firewall rules block unauthenticated external access to camera management.
  • Track vendor advisories for a documented fixed firmware version.
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-44355 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-44355Attack 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
ReolinkRLC-410Wv3.0.0.136_20121102Listed
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.