Cyber Resilience

CVE-2024-28640

Memory Safety in Totolink X5000R Firmware 9.1.0u.6118_b20201102

Memory Safety
Published
16 March 2024
Modified
17 June 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.14 96th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2024-28640 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Totolink X5000R Firmware. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 4% 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 SA-8 (Security and Privacy Engineering Principles) — 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.

CVE-2024-28640 is a buffer overflow vulnerability, tracked under CWE-125 as an out-of-bounds read, that affects the TOTOLINK X5000R router running firmware V9.1.0u.6118-B20201102 and the A7000R router running V9.1.0u.6115-B20201022. The flaw resides in handling of the command field and carries a CVSS 3.1 base score of 7.5, reflecting network-accessible exploitation with no required credentials or user interaction that results in high impact to availability.

An unauthenticated remote attacker can send a crafted command value to the affected devices, triggering the overflow and causing a denial-of-service condition that disrupts router operation. No authentication or local access is needed, allowing exploitation from anywhere on the network path to the device’s management interface.

Public references point to GitHub repositories documenting the TOTOLINK issues, but they contain no vendor advisory, firmware patch, or mitigation guidance. The EPSS score currently stands at 0.1705 with a recorded peak of 0.1742, indicating moderate and relatively stable exploitation interest since disclosure.

EU & UK References

Vulnerability Data

Buffer Overflow vulnerability in TOTOLink X5000R V9.1.0u.6118-B20201102 and A7000R V9.1.0u.6115-B20201022 allows a remote attacker to cause a denial of service (D0S) via the command field.

CWE(s)
CWE-125

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 →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
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-2023-36950Same product: Totolink A7000R
CVE-2023-45984Same product: Totolink A7000R
CVE-2023-45985Same product: Totolink A7000R
CVE-2023-36947Same product: Totolink A7000R
CVE-2024-28639Same product: Totolink A7000R
CVE-2024-34200Same vendor: Totolink
CVE-2023-33485Same product: Totolink X5000R
CVE-2023-49417Same product: Totolink A7000R
CVE-2023-49418Same product: Totolink A7000R
CVE-2023-33487Same product: Totolink X5000R

Affected Assets

totolink
x5000r firmware
9.1.0u.6118_b20201102
totolink
a7000r firmware
9.1.0u.6115_b20201022

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

SC-39 Process Isolation partial match

Process isolation confines the effects of an out-of-bounds read to the compromised process.

SI-10 Information Input Validation partial match

Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.

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 such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
prevents

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

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 in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.

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

Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

References