Skip to main content
CVE-2025-6121VulnerabilityPublished

CVE-2025-6121: D-Link DIR-632 · Stack-based Buffer Overflow

Affects D-Link DIR-632Source CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical · end of life, no fix coming : replace or isolate D-Link DIR-632; no fix will be released.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.7% chance of exploitation in 30 days – higher than 86% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
None coming – the product is end of life
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

No fix will be released: D-Link DIR-632 is end of life. Replace it, or isolate it from untrusted networks until you can.

AI-suggested

Given the absence of official patches, European organizations should prioritize the following practical mitigation steps: 1) Immediate identification and inventory of all D-Link DIR-632 devices running firmware FW103B08 within their networks. 2) Where possible, replace affected routers with newer, supported models that receive regular security updates. 3) If replacement is not immediately feasible, isolate the vulnerable devices by segmenting them into dedicated network zones with strict access controls to limit exposure. 4) Disable remote management interfaces and restrict administrative access to trusted internal IP addresses only. 5) Implement network-level protections such as intrusion detection/prevention systems (IDS/IPS) configured to detect anomalous HTTP POST requests with suspicious Content-Length headers. 6) Monitor network traffic for unusual patterns indicative of exploitation attempts, including unexpected crashes or reboots of the router. 7) Educate users and IT staff about the risks associated with legacy network devices and the importance of timely hardware lifecycle management. 8) Consider deploying compensating controls like VPNs or encrypted tunnels to protect sensitive communications passing through vulnerable routers. These steps go beyond generic advice by focusing on device-specific actions and network architecture adjustments to mitigate risk in the absence of vendor patches.

Description

A vulnerability, which was classified as critical, has been found in D-Link DIR-632 FW103B08. Affected by this issue is the function get_pure_content of the component HTTP POST Request Handler. The manipulation of the argument Content-Length leads to stack-based buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

References

Community reviews

Loading reviews…