LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35399: TOTOLINK CP900L v4.1.5cu.798_B20221228 was discovered to contain a stack overflow via the password paramete...

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

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
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-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.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-35399 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2024-35399Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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

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.

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.