Loading vulnerability…
A stack-based buffer overflow exists in the results.stm component of Sambar Server versions prior to 6.0 production release. The vulnerability is triggered by sending an HTTP POST request with an excessively long query parameter, which overflows a stack buffer.
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 exploit module targeting a buffer overflow vulnerability in the Sambar 6 web server's /search/results.stm application (CVE-2004-2086). The exploit works by sending a specially crafted HTTP POST request to the vulnerable endpoint, overflowing a buffer and allowing arbitrary code execution. The payload is inserted into multiple HTTP headers and POST data fields, and is customizable via Metasploit's payload system (up to 2000 bytes, with specific bad characters avoided). The module supports targeting Windows 2000 and Windows XP systems. The exploit may cause the Sambar service to crash even if exploitation is unsuccessful. The code is written in Ruby and follows the standard Metasploit module structure, with clear separation of initialization, vulnerability checking, and exploitation logic. The only fingerprintable endpoint is the /search/results.stm path on the target server, typically accessible via TCP port 80.
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.