Loading vulnerability…
A stack-based buffer overflow exists in the client acceptor daemon (CAD) scheduler component of the IBM Tivoli Storage Manager client and TSM Express. Crafted data in a TCP packet can overflow a stack buffer, allowing a remote attacker to execute arbitrary code. Affected versions include IBM Tivoli Storage Manager 5.3 before 5.3.6.7, 5.4 before 5.4.3, 5.5 before 5.5.2.2, and 6.1 before 6.1.0.2, as well as TSM Express versions 5.3.3.0 through 5.3.6.6.
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 (CVE-2009-3853) in the IBM Tivoli Storage Manager Express CAD Service (dsmcad.exe) on Windows. The exploit works by sending a specially crafted 'ping' packet to the service's default TCP port (1582), causing a buffer overflow and allowing arbitrary code execution. The module supports customizable Metasploit payloads (up to 380 bytes) and leverages SEH (Structured Exception Handler) overwrite techniques. The exploit requires the CAD service to be in a specific state (CadWaitingStatus = 1), which is only achievable when the TSM server is running. The repository is structured as a single Ruby file compatible with the Metasploit framework, and is operational, providing a working exploit for the specified vulnerability and product 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.