Cyber Resilience

CVE-2024-35387

Memory Safety in Totolink Lr350 Firmware 9.3.5u.6369_b20220309

Memory Safety
Published
24 May 2024
Modified
04 April 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.061 93th percentile
Risk Priority 80 floored blend · peak EPSS

Summary

CVE-2024-35387 is a critical-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Totolink Lr350 Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

TOTOLINK LR350 firmware version V9.3.5u.6369_B20220309 contains a stack-based buffer overflow vulnerability in the loginAuth function. The flaw is triggered when the http_host parameter is processed, allowing an attacker to overwrite the stack and potentially corrupt memory. The issue is tracked as CVE-2024-35387 with a CVSS 3.1 score of 9.8 and is classified under CWE-121.

An unauthenticated attacker with network access can exploit the vulnerability by sending a crafted HTTP request containing an oversized or malicious http_host value. Successful exploitation can lead to arbitrary code execution, full device compromise, or a denial-of-service condition without any user interaction or credentials.

Public details are available in a GitHub vulnerability report that demonstrates the flaw through proof-of-concept input. The EPSS score has remained modest, reaching a peak of 0.0996 and currently sitting at 0.0786, indicating limited observed exploitation interest to date. No vendor advisory or firmware update information is referenced in the available sources.

EU & UK References

Vulnerability Data

TOTOLINK LR350 V9.3.5u.6369_B20220309 was discovered to contain a stack overflow via the http_host parameter in the function loginAuth.

CWE(s)
CWE-121

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-63465Same product: Totolink Lr350
CVE-2025-63463Same product: Totolink Lr350
CVE-2025-63467Same product: Totolink Lr350
CVE-2025-63466Same product: Totolink Lr350
CVE-2025-63468Same product: Totolink Lr350
CVE-2025-63469Same product: Totolink Lr350
CVE-2024-34308Same product: Totolink Lr350
CVE-2025-63464Same product: Totolink Lr350
CVE-2024-35099Same product: Totolink Lr350
CVE-2026-1157Same product: Totolink Lr350

Affected Assets

totolink
lr350 firmware
9.3.5u.6369_b20220309

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can discover stack-buffer overflows before deployment.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from exceeding stack buffer bounds.

SI-16 Memory Protection good match

Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices directly prevent introduction of stack buffer overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.

PR.PS-02 partial match
prevents

Patching eliminates known instances of the weakness after discovery.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing (fuzzing, static analysis) detects stack overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates buffer-safety practices that directly prevent stack overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify buffer-size and input-validation rules.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include memory-safety and least-privilege stack usage.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.

A.8.32 Change management none match
none

Change-management gates can enforce security reviews that catch buffer issues.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. prevents CWE-121
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-121

References