Loading vulnerability…
A command injection vulnerability exists in TOTOLINK A6000R firmware version V1.0.1-B20201211.2000. The vulnerability is present in the webcmd function, where the cmd parameter is not properly sanitized, allowing attackers to inject arbitrary system commands.
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 proof-of-concept (POC) exploit for CVE-2024-41319, a command execution vulnerability in the TOTOLINK A6000R router. The main file, 'TOTOLINK_poc.py', is a Python script that allows the user to specify a single target URL or a file containing multiple URLs. For each target, the script sends a crafted HTTP GET request to the '/cgi-bin/luci/admin/mtk/webcmd' endpoint with a command injection payload that writes the output of the 'ls' command to '/www/555.txt' on the device. It then attempts to retrieve this file to verify successful command execution. The script uses multithreading to process multiple targets efficiently. The repository also includes a README.md with usage instructions and examples. No hardcoded IPs or domains are present; the script is designed for user-supplied targets. The exploit demonstrates the vulnerability but does not provide a weaponized or post-exploitation payload.
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.