A stack-based buffer overflow exists in Novell GroupWise Messenger versions prior to 2.0 Public Beta 2. The vulnerability is triggered when a remote attacker sends an overly long Accept-Language header value lacking a comma or semicolon, causing a buffer overflow and allowing for the execution of arbitrary code on the target system.
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 exploit module targeting a stack buffer overflow vulnerability in Novell GroupWise Messenger Server v2.0 (CVE-2006-0992). The exploit works by sending a specially crafted HTTP GET request to the server's Accept-Language header, overflowing the stack and allowing arbitrary code execution. The module is written in Ruby and leverages Metasploit's exploit framework, specifically the Remote::Tcp mixin. The exploit is operational, providing a shellcode payload (with restrictions due to bad characters) that is injected into the vulnerable header. The default target port is TCP 8300. The code is structured as a typical Metasploit module, with initialization, option registration, and an exploit method that crafts and sends the malicious request. The exploit is not a detection script and is not fake; it is a real exploit for a known vulnerability.
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.