Loading vulnerability…
A stack-based buffer overflow exists in the Web Server service of IBM Lotus Domino versions prior to 7.0.3 FP1 and 8.x prior to 8.0.1. The vulnerability is triggered by sending a long Accept-Language HTTP header, which can overflow a stack buffer and potentially allow remote attackers to crash the daemon or execute 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.
This repository contains a single Metasploit module that exploits a stack buffer overflow vulnerability (CVE-2008-2240) in the IBM Lotus Domino Web Server (versions prior to 7.0.3FP1 and 8.0.1) on Windows platforms. The exploit works by sending a specially crafted HTTP GET request with an overly long 'Accept-Language' header to the target server, causing a buffer overflow and allowing execution of arbitrary code. The module supports multiple target configurations, including different Windows versions and NX (No eXecute) protections. The payload is customizable via Metasploit and can be any compatible shellcode (e.g., reverse shell, meterpreter). The only endpoint directly referenced is a randomized .nsf file path, which is used to trigger the vulnerability. The exploit is operational and provides remote code execution capabilities. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.