Loading vulnerability…
A directory traversal vulnerability exists in the TFTP Server 1.0.0.24 component of Ipswitch WhatsUp Gold. The vulnerability is due to insufficient sanitization of the Filename field in RRQ (Read Request) operations, allowing remote attackers to include '..' sequences and access arbitrary files on the server's filesystem.
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 (1 hidden).
This repository contains a single Metasploit auxiliary scanner module targeting a directory traversal vulnerability (CVE-2011-4722) in the TFTP service of IpSwitch WhatsUp Gold. The module exploits the vulnerability by sending a specially crafted TFTP read request with a filename containing directory traversal sequences (e.g., ../../../../windows/win.ini), allowing the attacker to retrieve arbitrary files from the target system. The exploit operates over UDP port 69 (TFTP) and is designed to work against default configurations where write requests are forbidden but read requests are allowed. The module can save the retrieved file to disk for further analysis. The code is written in Ruby and follows the standard Metasploit module structure, with options to specify the target file and whether to save the output. No remote code execution is possible with this exploit; its impact is limited to unauthorized file disclosure.
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.