Loading vulnerability…
GNU Wget versions before 1.18 improperly handle an HTTP request redirected to a crafted FTP resource. A remote server can exploit this redirect handling to cause Wget to write to arbitrary local files.
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 (2 hidden).
This repository contains an exploit for CVE-2016-4971, targeting Wget versions 1.18 and 1.14-13.el7 on Linux. The exploit leverages a vulnerability in Wget's handling of FTP redirects to achieve arbitrary file upload on the victim system. The main exploit logic is implemented in 'exploit_wget.py', which acts as an HTTP server. When a vulnerable Wget client requests a file, the server responds with a redirect to an attacker-controlled FTP server, causing Wget to upload sensitive files (such as /etc/passwd or /etc/shadow) and to write a malicious cron job to /etc/cron.d/wget-root-shell. This cron job executes a command as root, demonstrating code execution by writing the output of 'id' to /root/hacked-via-wget. The 'faststart_exploit.sh' script automates the setup by starting a Python-based FTP server and launching the exploit server. The repository is operational and demonstrates a real-world attack chain, including exfiltration of sensitive files and privilege escalation via cron job injection. Key fingerprintable endpoints include the cron job file, exfiltrated files, and the network ports used for the attack.
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.