Stack-based buffer overflow in the Backup Agent for Microsoft SQL Server component of Computer Associates BrightStor ARCserve Backup Agent for SQL Server 11.0. The agent fails to properly bound-check a long string received over the network, allowing a remote attacker to overflow a stack buffer by sending an overly long string to the service listening on TCP port 6070 or 6050, potentially resulting in execution of attacker-controlled code in the context of the Backup Agent process.
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 (Ruby file) that exploits a buffer overflow vulnerability (CVE-2005-1272) in the CA BrightStor Agent for Microsoft SQL Server. The exploit targets the service running on TCP port 6070 and is capable of delivering arbitrary payloads (such as reverse shells) to the vulnerable system. The module supports multiple target versions, including specific versions of ARCServe and various Windows operating systems. The exploit works by sending a specially crafted buffer to the service, overwriting the return address to redirect execution to the injected payload. The code is operational and leverages the Metasploit framework for payload handling and session management. No hardcoded IP addresses or URLs are present; the only fingerprintable endpoint is the default TCP port 6070.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.