Multiple D-Link routers, including DIR-600 rev B through 2.14b01 and DIR-300 rev B through 2.13, contain an unauthenticated OS command injection vulnerability in the web management interface. The flaw is in command.php, which improperly handles the POST parameter cmd and allows attacker-supplied input to be executed by the underlying operating system. Because the vulnerable endpoint is reachable without authentication, a remote attacker can submit crafted requests directly to command.php and cause arbitrary OS command execution. The provided description specifically notes that the issue can be used to spawn a Telnet service on an attacker-specified port, resulting in persistent interactive shell access as root.
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 auxiliary module targeting D-Link DIR-600 and DIR-300 routers (rev B, specific firmware versions) vulnerable to unauthenticated OS command injection (CVE-2013-10069). The exploit works by sending a POST request to the /command.php endpoint, which is accessible without authentication, with arbitrary shell commands. The module allows the user to specify any command (default: 'cat var/passwd') and checks for successful exploitation by looking for a specific marker in the response. The exploit can be used to start a telnet daemon for remote shell access or to read sensitive files. The code is written in Ruby and leverages the Metasploit framework's HTTP client utilities. No detection or fake code is present; this is a functional exploit module.
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.