CVE-2024-48150: n/a
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 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 2026-10-25.
What to do
AI-suggested
Given the absence of an official patch, organizations should implement immediate compensating controls to reduce exposure. First, disable remote management interfaces on the D-Link DIR-820L routers to prevent external access to vulnerable services. Second, segment the network to isolate the router from critical assets and limit potential lateral movement if compromised. Third, employ strict firewall rules to restrict inbound traffic to the router, allowing only trusted IP addresses if remote access is necessary. Fourth, monitor network traffic for unusual patterns or signs of exploitation attempts, such as unexpected outbound connections or anomalous payloads targeting the router. Fifth, consider replacing or upgrading affected devices to models with updated firmware or from vendors with active security support. Finally, maintain vigilance for firmware updates from D-Link and apply them promptly once available. Network administrators should also educate users about the risks and encourage regular device audits to identify vulnerable hardware.
Description
D-Link DIR-820L 1.05B03 has a stack overflow vulnerability in the sub_451208 function.