LiveActive security incident?Get immediate response
CVE Record

CVE-2022-29641: TOTOLINK A3100R V4.1.2cu.5050_B20200504 and V4.1.2cu.5247_B20211129 were discovered to contain a stack over...

TOTOLINK A3100R V4.1.2cu.5050_B20200504 and V4.1.2cu.5247_B20211129 were discovered to contain a stack overflow via the startTime and endTime parameters in the function setParentalRules. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted POST request.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a denial-of-service risk in two TOTOLINK A3100R firmware builds. A malformed request to parental-control handling can overflow the device stack and disrupt service. Public evidence does not provide a CVSS score, vendor fix, or confirmation of real-world exploitation.

Executive priority

Handle as an inventory and exposure-reduction item unless affected routers are internet-managed or business-critical. Urgency increases if listed firmware is deployed in exposed sites with limited redundancy.

Technical view

The reported flaw is a stack overflow in setParentalRules, triggered through the startTime and endTime parameters. The CVE description says a crafted POST request can cause denial of service on TOTOLINK A3100R V4.1.2cu.5050_B20200504 and V4.1.2cu.5247_B20211129.

Likely exposure

Exposure is most relevant where affected TOTOLINK A3100R devices run the listed firmware and expose management or parental-control functions to untrusted users or networks. The provided CVE data does not identify broader products or versions.

Exploitation context

The source bundle describes a denial-of-service trigger but does not cite active exploitation, CISA KEV listing, exploit maturity, authentication requirements, or network reachability conditions. Treat exploitation status as unconfirmed.

Researcher notes

Evidence is sparse: no CVSS, CWE, vendor advisory, or confirmed patch is included. The GitHub reference appears to be the primary technical disclosure; avoid assuming affected scope beyond the two named builds.

Mitigation direction

  • Check TOTOLINK guidance for firmware updates or replacement recommendations.
  • Restrict router management interfaces to trusted administrative networks.
  • Disable remote administration where operationally feasible.
  • Isolate or replace affected devices if no maintained firmware is available.

Validation and detection

  • Inventory TOTOLINK A3100R devices in the environment.
  • Record firmware build strings from device management interfaces.
  • Compare builds against V4.1.2cu.5050_B20200504 and V4.1.2cu.5247_B20211129.
  • Review whether management access is reachable from untrusted networks.
  • Monitor affected devices for unexpected reboots or service disruption.
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.

cve · low confidence lookup

CVE-2022-29641 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
2Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.