Loading vulnerability…
A buffer overflow vulnerability exists in the web proxy component of GateKeeper Pro version 4.7. The vulnerability is triggered when a remote attacker sends a specially crafted, excessively long GET request to the proxy, resulting in a buffer overflow condition. This flaw allows for the execution of arbitrary code in the context of the vulnerable service.
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 exploit module targeting a stack buffer overflow vulnerability in Proxy-Pro Professional GateKeeper 4.7 (CVE-2004-0326). The exploit works by sending a specially crafted, overly long HTTP GET request to the service's default TCP port 3128. The buffer overflow allows the attacker to execute arbitrary code with the privileges of the vulnerable service. The module is written in Ruby and leverages the Metasploit framework's payload system, allowing the user to select from a variety of payloads (such as reverse shells or Meterpreter sessions). The exploit is operational and requires the target to be running the vulnerable version of the software, listening on the default port. No hardcoded IPs or URLs are present; the only fingerprintable endpoint is the TCP port 3128. The repository structure is typical for a Metasploit module, with all logic contained in a single Ruby file.
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.