Security readout for executives and security teams
Plain-English summary
CVE-2024-35399 is a high-severity flaw in TOTOLINK CP900L firmware v4.1.5cu.798_B20221228. A crafted login password value can trigger a stack overflow, potentially compromising confidentiality, integrity, and availability on reachable devices.
Executive priority
Prioritize identification and containment where CP900L devices support business networks. The technical impact is high, but available evidence does not confirm internet-scale exposure, active exploitation, or an official fix.
Technical view
The CVE describes a CWE-121 stack-based buffer overflow in the loginAuth function through the password parameter. CVSS 3.1 is 8.8 with adjacent-network attack vector, low complexity, no privileges, no user interaction, and high impact to C/I/A.
Likely exposure
Known exposure is limited to TOTOLINK CP900L v4.1.5cu.798_B20221228 as stated in the CVE description. Structured affected vendor/product/CPE data is not provided.
Exploitation context
The record is not listed as CISA KEV in the provided bundle, and no cited source confirms active exploitation. The adjacent-network vector suggests risk is highest on local or nearby network segments.
Researcher notes
Evidence is narrow: one CVE description and one public GitHub report reference. The CVE lacks structured CPEs and remediation metadata, so scope should be validated by model and firmware evidence rather than assumptions.
Mitigation direction
Check TOTOLINK support channels for firmware updates or advisories.
Restrict device administration access to trusted management networks.
Remove exposed or unnecessary CP900L devices from production networks.
Segment affected devices from sensitive business systems.
Replace devices if no vendor-supported fix is available.
Validation and detection
Inventory TOTOLINK CP900L devices and record firmware versions.
Confirm whether any device runs v4.1.5cu.798_B20221228.
Review network reachability to device login interfaces.
Check logs for unusual login failures, crashes, or reboots.
Track CVE and vendor sources for remediation updates.
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-121: 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.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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
3Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.