A buffer overflow vulnerability exists in the Discovery Service component of BrightStor ARCserve Backup versions 9.0 through 11.1. The vulnerability is triggered when a remote attacker sends a specially crafted large packet to TCP port 41523, resulting in a buffer overflow condition. This allows the attacker to execute arbitrary commands on the affected system. This issue is distinct from CVE-2005-0260.
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/brightstor/discovery_tcp.rb) that exploits a buffer overflow vulnerability (CVE-2005-2535) in the CA BrightStor Discovery Service running on Windows. The exploit targets the service listening on TCP port 41523 and leverages a stack-based buffer overflow in the cheyprod.dll component. The module supports multiple known vulnerable versions of the DLL, each with specific return addresses and offsets. The exploit is capable of delivering arbitrary Metasploit payloads (default space: 2048 bytes), allowing for code execution on the target system. The module includes a check method to detect the presence of the vulnerable service by sending specific probes and analyzing the responses. The exploit is operational and can be used to gain remote code execution on affected systems. No hardcoded IPs or domains are present; the main fingerprintable endpoint is the TCP port 41523 on the target host.
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.