CVE-2025-55599
Memory Safety in Dlink Dir-619L Firmware 2.06b01
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-55599 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Dlink Dir-619L Firmware. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 36th percentile by exploit likelihood (below the median); 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.
CVE-2025-55599 is a buffer overflow vulnerability affecting the D-Link DIR-619L router running firmware version 2.06B01. The issue resides in the formWlanSetup function, which can be triggered via the f_wds_wepKey parameter. Classified under CWE-787 (Out-of-bounds Write) and CWE-120 (Buffer Copy without Checking Size of Input), it has a CVSS v3.1 base score of 7.5, reflecting network accessibility, low attack complexity, no required privileges or user interaction, unchanged scope, and high impact on availability with no impact on confidentiality or integrity.
Remote, unauthenticated attackers can exploit this vulnerability over the network by sending specially crafted requests to the affected function. Successful exploitation leads to a denial-of-service condition, such as device crashes or reboots, disrupting network availability without compromising data or enabling code execution.
Advisories and further details are available in the referenced GitHub repository at https://github.com/wudipjq/my_vuln/blob/main/D-Link6/vuln_65/65.md, which documents the vulnerability analysis. No official patches or mitigations from D-Link are specified in the available information.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-25590
Vulnerability Data
D-Link DIR-619L 2.06B01 is vulnerable to Buffer Overflow in the formWlanSetup function via the parameter f_wds_wepKey.
- 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 evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Input validation directly enforces size checks before buffer copies.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Engineering principles require bounds checking and safe buffer handling in design.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
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 (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Change management can enforce review gates that catch unsafe memory operations before deployment.