CVE-2024-52755: D-LINK DI-8003 · Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 3.5 Low.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-52755, organizations should first restrict access to the router's management and VPN configuration interfaces to trusted networks and authorized personnel only. Network segmentation can limit exposure by isolating the device from untrusted or public networks. Monitoring network traffic for unusual activity around the IPsec VPN services may help detect exploitation attempts. Since no patches are currently available, organizations should engage with D-LINK support to inquire about firmware updates addressing this vulnerability. If possible, consider upgrading to newer, supported router models with improved security. Implementing strict input validation and secure coding practices in firmware development is critical for vendors to prevent similar vulnerabilities. Additionally, maintaining up-to-date network device inventories and vulnerability management processes will help identify and remediate affected devices promptly once patches are released.
Description
D-LINK DI-8003 v16.07.26A1 was discovered to contain a buffer overflow via the host_ip parameter in the ipsec_road_asp function.