CVE-2025-6163
Memory Safety in Totolink A3002Ru Firmware 3.0.0-b20230809.1615
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-6163 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Totolink A3002Ru Firmware. Its CVSS base score is 7.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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.
A vulnerability classified as critical was found in the TOTOLINK A3002RU firmware version 3.0.0-B20230809.1615. It resides in an unknown function of the file /boafrm/formMultiAP within the HTTP POST Request Handler component. The issue stems from improper handling of the submit-url argument, resulting in a buffer overflow condition tracked under CWE-119 and CWE-120.
An attacker with network access and valid credentials can send a crafted HTTP POST request to trigger the overflow remotely. Successful exploitation grants the ability to execute arbitrary code or crash the affected device, as demonstrated by a publicly disclosed proof-of-concept.
The EPSS score has remained essentially flat near 0.0136 since disclosure, with no indication of rising exploitation interest. Public references consist of a GitHub repository containing the proof-of-concept and VulDB entries that document the flaw, but no vendor advisory or patch information is provided in the available sources.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18475
Vulnerability Data
A vulnerability was found in TOTOLINK A3002RU 3.0.0-B20230809.1615 and classified as critical. Affected by this issue is some unknown functionality of the file /boafrm/formMultiAP of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer…
more
overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.3.2V5.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.
Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.
Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding 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.
Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.
Vulnerability scanning and code analysis directly surface buffer-boundary flaws.
Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.
Developer training on secure coding reduces introduction of memory-buffer errors.
Patching replaces vulnerable code containing buffer-boundary defects.
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 catches out-of-bounds accesses before release, covering most instances of the weakness.
Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.
Application security requirements can specify memory-safety rules, but do not prescribe implementation details.
Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.