CVE-2012-10021 is a stack-based buffer overflow in D-Link DIR-605L Wireless N300 Cloud Router firmware versions 1.12 and 1.13. The vulnerability is in the getAuthCode() function and is triggered through the /goform/formLogin endpoint when the device processes attacker-controlled CAPTCHA data supplied via the FILECODE parameter. The flaw is caused by unsafe use of sprintf() on user-supplied input without proper bounds checking, allowing data to overflow a stack buffer. Because the vulnerable code is reachable remotely and does not require authentication, an attacker can send a crafted request to corrupt stack memory and redirect execution flow.
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_dir605l_captcha_bof.rb) targeting a remote code execution vulnerability (CVE-2012-10021) in D-Link DIR-605L routers (firmware 1.12 and 1.13). The exploit abuses a buffer overflow in the captcha handling code of the router's web interface (Boa web server) by sending a specially crafted POST request to /goform/formLogin. The module first checks for the presence of the vulnerable device by sending a GET request to /comm.asp and verifying the model and server banner. If the target is vulnerable, the exploit sends a payload (customizable MIPSBE shellcode) via the FILECODE POST parameter, resulting in arbitrary code execution as root. The module is operational and allows for custom payloads, but is ranked as 'Manual' due to limited testing environments. The code is written in Ruby and is structured as a standard Metasploit exploit module.
3 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.