Loading vulnerability…
A stack-based buffer overflow exists in the do_hnap function of 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. The vulnerability is triggered by a long Content-Length header in a GetDeviceSettings action within an HNAP request, allowing remote attackers to overflow a stack buffer and potentially execute arbitrary code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/linux/http/dlink_hnap_bof.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2014-3936) in the HNAP handler of certain D-Link devices (notably DIR-505 and DSP-W215). The exploit works by sending a specially crafted HTTP POST request to the /HNAP1/ endpoint, triggering the overflow and enabling remote code execution as root. The module includes automatic fingerprinting of the device and firmware version via HTTP GET requests to /HNAP1/, and supports multiple target versions with specific offsets and return addresses. The payload is delivered using Metasploit's CmdStager, allowing arbitrary shell commands to be executed on the device. The code is written in Ruby and is fully integrated into the Metasploit framework, making it operational and ready for use against vulnerable targets.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.