CVE-2024-54887
Memory Safety in Tp-Link Tl-Wr940N Firmware ≤ 3.16.9
Raw vector
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-54887 is a high-severity Classic Buffer Overflow (CWE-120) vulnerability in Tp-Link Tl-Wr940N. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 8% 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.
CVE-2024-54887 is a buffer overflow vulnerability (CWE-120) in TP-Link TL-WR940N V3 and V4 routers running firmware version 3.16.9 and earlier. The flaw occurs in the handling of the dnsserver1 and dnsserver2 parameters on the /userRpm/Wan6to4TunnelCfgRpm.htm webpage, which can be triggered to overwrite memory boundaries.
An attacker with low privileges (PR:L) who is adjacent to the device on the network (AV:A) can exploit this with low attack complexity (AC:L) and no user interaction (UI:N). Successful exploitation enables arbitrary code execution in the context of the root user, granting high impacts on confidentiality, integrity, and availability (CVSS:3.1 score of 8.0).
Advisories and additional details are referenced at http://tp-link.com and https://github.com/JBince/vulnerability-research/tree/main/CVE-2024-54887, which include vulnerability research and likely mitigation guidance from the vendor.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52689
Vulnerability Data
TP-Link TL-WR940N V3 and V4 with firmware 3.16.9 and earlier contain a buffer overflow via the dnsserver1 and dnsserver2 parameters at /userRpm/Wan6to4TunnelCfgRpm.htm. This vulnerability allows an authenticated attacker to execute arbitrary code on the remote device in the context of…
more
the root user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can find missing size checks before deployment.
Input validation directly enforces size checks before buffer copies.
Engineering principles require bounds checking and safe buffer handling in design.
Memory protection limits the impact of an overflow once it occurs.
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.
Secure development practices directly enforce bounds checking and input validation that prevent classic buffer overflows.
Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.
Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.
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.
Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.
Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.
Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.
Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.
Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.