CVE-2023-45580
Memory Safety in Dlink Di-7003G Firmware ≤ 23.08.25d1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-45580 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Dlink Di-7003G 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 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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 buffer overflow vulnerability exists in multiple D-Link router models including DI-7003GV2.D1 versions 23.08.25D1 and earlier, DI-7100G+V2.D1 and DI-7100GV2.D1 versions 23.08.23D1 and earlier, DI-7200G+V2.D1 and DI-7200GV2.E1 versions 23.08.23D1/E1 and earlier, and DI-7300G+V2.D1 and DI-7400G+V2.D1 versions 23.08.23D1 and earlier. The flaw, tracked as CWE-787, resides in the ddns.asp function and can be triggered through the wild, mx, and related parameters.
Unauthenticated remote attackers can send specially crafted requests over the network to trigger the overflow and achieve arbitrary code execution on the affected devices, which carry a CVSS 3.1 score of 9.8. The provided references consist of GitHub submissions detailing the issue but contain no vendor advisory, firmware update, or mitigation guidance.
EPSS scores for the CVE have remained in a narrow band between a peak of 0.0912 and a current value of 0.0810 with no material upward trajectory from a low baseline.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-49872
Vulnerability Data
Buffer Overflow vulnerability in D-Link device DI-7003GV2.D1 v.23.08.25D1 and before, DI-7100G+V2.D1 v.23.08.23D1 and before, DI-7100GV2.D1 v.23.08.23D1, DI-7200G+V2.D1 v.23.08.23D1 and before, DI-7200GV2.E1 v.23.08.23E1 and before, DI-7300G+V2.D1 v.23.08.23D1, and DI-7400G+V2.D1 v.23.08.23D1 and before allows a remote attacker to execute arbitrary code via…
more
the wild/mx and other parameters of the ddns.asp function
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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.
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.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.