A directory traversal vulnerability exists in Majordomo2 (up to version 20110203) in the _list_file_get function of lib/Majordomo.pm. The vulnerability is triggered via the 'extra' parameter to the 'help' command, where improper sanitization allows sequences like './.../' to bypass the intended regex filter and produce '..' (dot dot) sequences. This enables remote attackers to read arbitrary files on the server. The issue is a result of an incomplete fix for CVE-2011-0049.
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 in Majordomo2's _list_file_get() function. The exploit works by sending HTTP GET requests to a vulnerable Majordomo2 endpoint, appending directory traversal sequences to the URI in order to access arbitrary files on the server. By default, it attempts to retrieve the 'config.pl' file, but the file and traversal depth are configurable. The module reports success if it retrieves the file and stores it as loot in Metasploit. The code is written in Ruby and leverages Metasploit's HTTP client and scanner mixins. The main attack vector is network-based, exploiting a web-accessible CGI endpoint. The module references CVE-2011-0049 and CVE-2011-0063, and is operational, providing file disclosure capabilities if the target is vulnerable.
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.