A stack-based buffer overflow exists in the alphapd web server component of multiple D-Link DCS series Wi-Fi cameras. The vulnerability is triggered when a remote, authenticated attacker sends an overly long string in the WEPEncryption parameter to the wireless.htm endpoint. This allows for overwriting of stack memory, potentially leading to arbitrary code execution. Affected models include DCS-5009L (1.08.11 and below), DCS-5010L (1.14.09 and below), DCS-5020L (1.15.12 and below), DCS-5025L (1.03.07 and below), DCS-5030L (1.04.10 and below), DCS-930L (2.16.01 and below), DCS-931L (1.14.11 and below), DCS-932L (2.17.01 and below), DCS-933L (1.14.11 and below), and DCS-934L (1.05.04 and below).
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 provides a Python 3 exploit for a buffer overflow vulnerability in the 'alphapd' HTTP server of multiple D-Link camera models (e.g., DCS-5020L, DCS-930L, DCS-932L, and others). The exploit targets the 'WEPEncryption' parameter in the 'wireless.htm' page, which is vulnerable to buffer overflow when supplied with an overly long value. The exploit is operational and allows remote code execution on the device, typically starting a telnet server for shell access. The exploit requires valid credentials (default: admin with blank password) and network access to the device's HTTP interface. The code is modular, with device- and version-specific ROP chains defined in separate files under 'DlinkExploit/overflows/'. The main entry point is 'exploit.py', which automates detection of the device model/version, constructs the appropriate overflow payload, and sends the exploit HTTP request. The repository also includes utility code for authentication and URL encoding. No hardcoded IPs or credentials are present; all are supplied at runtime. The exploit is not part of a framework and is a standalone operational 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.
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.