Loading vulnerability…
A stack-based buffer overflow exists in the Discovery Service component of BrightStor ARCserve Backup 11.1 and earlier. The vulnerability is triggered when a specially crafted, overly long packet is sent to UDP port 41524. The recvfrom call does not properly validate the length of incoming data, leading to a buffer overflow on the stack.
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 targeting a stack buffer overflow vulnerability in the CA BrightStor Discovery Service (CVE-2005-0260). The exploit works by sending a specially crafted UDP packet to port 41524 on the target Windows system, causing a buffer overflow and allowing arbitrary code execution. The module includes a check method that probes TCP port 41523 to verify the presence of the vulnerable service before launching the exploit. The payload is customizable and leverages Metasploit's payload system, supporting up to 2048 bytes (excluding null bytes). The exploit specifically targets two known vulnerable versions of cheyprod.dll. The code is written in Ruby and follows the standard Metasploit module structure, making it operational and ready for use within the Metasploit framework.
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.