Multiple stack-based buffer overflows exist in Novell GroupWise Messenger (GWIM) Client prior to version 2.0.3 HP1 for Windows. The vulnerability is triggered when the client processes spoofed server responses containing an overly long string after the NM_A_SZ_TRANSACTION_ID field name, leading to a stack overflow and potential execution of arbitrary code.
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 stack buffer overflow vulnerability (CVE-2008-2703) in the Novell GroupWise Messenger Client (versions 1.0 and 2.0) on Windows. The exploit works by acting as a malicious server that listens for incoming connections (default port 8300) from vulnerable clients. When a client connects, the module sends a specially crafted HTTP response containing a buffer overflow and a customizable payload. If the client is vulnerable, the payload is executed with the privileges of the client process, allowing for arbitrary code execution. The exploit is operational and allows for any Metasploit payload to be delivered, making it flexible for post-exploitation activities. The code is written in Ruby and follows the standard Metasploit module structure, with all logic contained in a single 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.