Loading vulnerability…
CVE-2012-10058 affects RabidHamster R4 v1.25. The vulnerability is a stack-based buffer overflow caused by unsafe use of sprintf() while logging malformed HTTP requests. A remote attacker can trigger the flaw by sending a specially crafted HTTP URI, causing attacker-controlled data to overflow a stack buffer during the logging path. Successful exploitation can lead to arbitrary code execution in the context of the web server process.
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 module (modules/exploits/windows/http/rabidhamster_r4_log.rb) that exploits a stack-based buffer overflow vulnerability in the RabidHamster R4 web server (version 1.25) on Windows. The exploit works by sending a specially crafted HTTP GET request to the server's root URI (default port 8888), triggering a buffer overflow in the server's log generation routine. This allows the attacker to execute arbitrary code with the privileges of the web server process. The module allows the user to supply a custom Metasploit payload, making it possible to achieve various post-exploitation goals such as spawning a shell. The module also includes a check method to verify if the target is running the vulnerable server by inspecting the 'Server' HTTP header. The exploit is operational and leverages a network-based attack vector, requiring only network access to the target service.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.