CVE-2016-11021 is an OS command injection vulnerability in D-Link DCS-930L devices before firmware version 2.12. The flaw is present in the setSystemCommand functionality, which insufficiently sanitizes or neutralizes attacker-controlled input supplied through the SystemCommand parameter before passing it to the underlying operating system for execution. A remote attacker can exploit this condition by sending a crafted request containing shell metacharacters or additional commands in that parameter, causing arbitrary command execution on the device.
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 targeting the D-Link DCS-930L Network Video Camera (firmware 2.01, fixed in 2.12) for authenticated remote command execution (CVE-2016-11021). The exploit works by logging into the camera's web interface using valid credentials, then exploiting a command injection vulnerability at the /setSystemCommand HTTP endpoint. The module sends a POST request to this endpoint to start a telnet daemon on a random high port, then connects to it to provide an interactive shell to the attacker. The code is written in Ruby and follows the standard Metasploit module structure, including options for HTTP credentials and telnet timeouts. The main exploit file is 'modules/exploits/linux/http/dlink_dcs_930l_authenticated_remote_command_execution.rb'. The exploit is operational, providing a working shell if the target is vulnerable and valid credentials are supplied.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.