A stack-based buffer overflow exists in DoubleTake.exe, a component of HP StorageWorks Storage Mirroring (SWSM) prior to version 4.5 SP2. The vulnerability is triggered when the application processes a specially crafted encoded authentication request, leading to a buffer overflow on the stack. This flaw allows remote attackers to execute arbitrary code on the affected 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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/misc/doubletake.rb) that exploits a stack buffer overflow vulnerability (CVE-2008-1661) in the authentication mechanism of NSI DoubleTake and HP StorageWorks Storage Mirroring Service. The exploit targets Windows systems running specific vulnerable versions (4.4.2, 4.5.0, 4.5.0.1819) of the software, connecting to the service on TCP port 1100. The module constructs a specially crafted authentication request that overflows a stack buffer, overwriting SEH and allowing execution of a customizable Metasploit payload (default space: 500 bytes, avoiding null bytes). The exploit is operational and provides remote code execution capabilities. The only fingerprintable endpoint is the TCP service on port 1100. 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.