Skip to content
Fencer Intel
critical 10.0

CVE-2014-3936 in the critical feed json

Stack-based buffer overflow in the do_hnap function in www/my_cgi.cgi in D-Link DSP-W215 (Rev.

published 12y ago modified 4mo ago also EUVD-2014-3873

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
76.6%
EPSS 76.6% chance of exploitation in 30 days, percentile 99.5%
public exploits
2
Metasploit and Exploit-DB

Summary

Stack-based buffer overflow in the do_hnap function in www/my_cgi.cgi in D-Link DSP-W215 (Rev. A1) with firmware 1.01b06 and earlier, DIR-505 with firmware before 1.08b10, and DIR-505L with firmware 1.01 and earlier allows remote attackers to execute arbitrary code via a long Content-Length header in a GetDeviceSettings action in an HNAP request.

Is CVE-2014-3936 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/linux/http/dlink_hnap_bof)
  2. Published

Exploit prediction

76.56% chance of exploitation in the next 30 days, higher than 99.5% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/linux/http/dlink_hnap_bof D-Link HNAP Request Remote Buffer Overflow metasploit exploit, normal rank, 2014-05-15
  • EDB-34064 D-Link HNAP - Request Remote Buffer Overflow (Metasploit) remote, 2014-07-14
  • devttys0.com http://www.devttys0.com/2014/05/hacking-the-d-link-dsp-w215-smart-plug referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/127427/D-Link-HNAP-Request-Remote-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/67651 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.