Loading vulnerability…
A remote buffer overflow vulnerability exists in MiniShare 1.4.1 and earlier, a minimal HTTP server for Windows. The vulnerability is triggered by sending a long HTTP GET request, specifically exploiting improper handling of address links, resulting in a buffer overflow. This allows an attacker to execute arbitrary code remotely. The exploit was confirmed on Windows XP SP1, Windows 2000 SP4, and Windows NT SP6 (all English versions).
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 a single Metasploit module (minishare_get_overflow.rb) that exploits a stack buffer overflow vulnerability (CVE-2004-2271) in the Minishare web server versions prior to 1.4.2 (specifically 1.4.1 is confirmed vulnerable). The exploit works by sending a specially crafted HTTP GET request with an overlong URI to the target Minishare server, causing a buffer overflow and allowing arbitrary code execution. The module supports multiple Windows targets (various versions and service packs) by using different return addresses for 'jmp esp' or similar instructions. The payload is fully customizable using Metasploit's payload system, enabling actions such as reverse shells or meterpreter sessions. The exploit is weaponized and ready for use within the Metasploit framework. The only fingerprintable endpoint is the HTTP interface of the Minishare server, which is targeted by the crafted GET request.
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.