LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35400: TOTOLINK CP900L v4.1.5cu.798_B20221228 was discovered to contain a stack overflow via the desc parameter in...

TOTOLINK CP900L v4.1.5cu.798_B20221228 was discovered to contain a stack overflow via the desc parameter in the function SetPortForwardRules

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-35400 affects the TOTOLINK CP900L firmware version named in the record. A malformed port-forwarding description can trigger a stack overflow, potentially disrupting device availability. The public record rates impact as medium, not data theft or privilege escalation.

Executive priority

Treat as a moderate infrastructure hygiene issue. Prioritize exposed or remotely managed devices first, because the known impact is availability disruption rather than confirmed compromise or data loss.

Technical view

The issue is a CWE-120 stack-based buffer overflow in SetPortForwardRules via the desc parameter on TOTOLINK CP900L v4.1.5cu.798_B20221228. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges or user interaction, unchanged scope, and low availability impact only.

Likely exposure

Exposure is likely limited to environments running the named TOTOLINK CP900L firmware, especially where router management or port-forwarding configuration paths are reachable from untrusted networks. The CVE affected-product metadata is incomplete.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. A public vulnerability report exists, but the provided evidence does not establish real-world exploitation, weaponized use, or a vendor-confirmed fix.

Researcher notes

The record names the vulnerable function and parameter but provides incomplete CPE and affected-product metadata. Analysis should stay scoped to the named CP900L firmware until vendor advisories or additional authoritative sources expand applicability.

Mitigation direction

  • Inventory TOTOLINK CP900L devices and confirm firmware version.
  • Restrict management access to trusted internal networks or VPN only.
  • Remove unnecessary internet exposure for router administration interfaces.
  • Check TOTOLINK guidance for fixed firmware or official mitigation.
  • Isolate or replace affected devices if no supported fix is available.

Validation and detection

  • Confirm whether any CP900L runs v4.1.5cu.798_B20221228.
  • Review firewall rules exposing management or configuration interfaces.
  • Check CVE and vendor sources for updated affected-version data.
  • Verify administrative access is limited to trusted operators.
  • Monitor affected devices for unexpected crashes or restarts.
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-120: 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-2024-35400 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2024-35400Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
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.