CVE-2014-125117 is a stack-based buffer overflow in the my_cgi.cgi component of certain D-Link devices, including DSP-W215 firmware version 1.02. A specially crafted HTTP POST request directed to the /common/info.cgi endpoint can trigger the overflow, allowing an unauthenticated remote attacker to execute code with system-level privileges.
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_dspw215_info_cgi_bof.rb) that exploits a stack-based buffer overflow vulnerability in the D-Link DSP-W215 smart plug (firmware v1.02) and potentially other D-Link devices. The vulnerability resides in the /common/info.cgi handler, which is accessible via HTTP. The exploit works by sending a specially crafted POST request to this endpoint, overflowing a buffer in the my_cgi.cgi component and hijacking execution to run arbitrary shell commands on the device. The module uses Metasploit's command stager to deliver the payload, which is executed as root on the target. The exploit is operational and provides remote code execution capabilities. The only fingerprintable endpoint is the /common/info.cgi path on the device's web interface. The code is written in Ruby and is structured as a standard Metasploit exploit module, with methods for checking target vulnerability, preparing the payload, and executing the exploit.
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.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.