Loading vulnerability…
SoftiaCom wMailServer versions 1.0 and 2.0 are vulnerable to a buffer overflow condition when processing large TCP packets that begin with a leading space. This flaw allows remote attackers to send specially crafted packets to the server, potentially causing the application to crash.
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 SoftiaCom WMailserver 1.0's SMTP service (CVE-2005-2287). The exploit works by sending a specially crafted payload to TCP port 25, overwriting the SEH frame and allowing arbitrary code execution. The module is written in Ruby and leverages Metasploit's Remote::Tcp and Remote::Seh mixins. It supports two main Windows targets: Windows 2000 Pro English and Windows XP Pro SP0/SP1 English. The payload is customizable (up to 600 bytes) and avoids specific bad characters. The exploit is operational and can be used to gain remote code execution on vulnerable systems running the specified WMailserver version.
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.