CVE-2014-4877 is an absolute path traversal vulnerability in GNU Wget versions before 1.16. When recursive retrieval is enabled, Wget incorrectly handles symbolic-link information returned in FTP LIST responses. A malicious FTP server can return two directory entries for the same filename, with one representing a symbolic link, causing Wget to write downloaded content to an arbitrary location writable by the user running Wget.
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 auxiliary module: 'modules/auxiliary/server/wget_symlink_file_write.rb'. The module exploits CVE-2014-4877, a vulnerability in GNU Wget (versions prior to 1.16) when used in recursive mode with an FTP server. The exploit works by running a malicious FTP server that, when accessed by a vulnerable wget client, uses symlinks to write arbitrary data to arbitrary files on the victim's filesystem. The attacker can specify both the file to overwrite (TARGET_FILE) and the data to write (TARGET_DATA). The module listens on a configurable port (default 2121) and provides instructions for the target to run a wget command against the attacker's server. The exploit is operational and provides a real-world arbitrary file write capability, but is not weaponized for mass exploitation. The code is written in Ruby and is designed to be run within the Metasploit framework.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.