A remote command execution vulnerability exists in TP-Link Archer C5 devices through firmware version V2_160201_US. The vulnerability is due to improper sanitization of shell metacharacters in the 'wan_dyn_hostname' field of the device's configuration file. An attacker with access to the web admin interface can upload a maliciously crafted configuration file (encrypted with key 478DA50BF9E3D2CF) to execute arbitrary commands on the device. The risk is exacerbated by the use of the default 'admin' password in some deployments.
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 proof-of-concept exploit for CVE-2018-19537, an authenticated remote code execution vulnerability in all published firmware versions of the TP-Link Archer C5 router. The exploit leverages the router's configuration file upload feature, which fails to properly sanitize parameters when restoring from a file. By decrypting a configuration file (using 'unbinify.py'), injecting a malicious shell command into the 'wan_dyn_hostname' parameter, and re-encrypting it (using 'binify.py'), an attacker can upload the file via the router's web interface. Upon reboot, the injected command is executed as root. The PoC demonstrates how to persistently execute arbitrary commands, including downloading and running further payloads from the internet. The repository includes two Python scripts for handling the router's DES-encrypted configuration files and a sample configuration file. The attack requires authenticated access to the router's web interface, but can be performed remotely if remote management is enabled. The exploit is impactful, providing persistent root access to the device.
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.