A stack-based buffer overflow exists in the Agent Browser component of Veritas Backup Exec versions 8.x prior to 8.60.3878 Hotfix 68 and 9.x prior to 9.1.4691 Hotfix 40. The vulnerability is triggered when a remote attacker sends a registration request containing an overly long hostname, which overflows a stack buffer and allows for arbitrary code execution.
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 exploit module targeting a stack buffer overflow vulnerability (CVE-2004-1172) in the Veritas Backup Exec Agent Browser service on Windows. The exploit works by sending a specially crafted agent registration request to the service on TCP port 6101, overflowing a stack buffer and overwriting the return address. Due to limited contiguous space for shellcode, a small 'findsock' stage is first sent, which then receives and executes the main payload (such as a reverse shell). The module supports multiple versions of the service (8.5, 8.6, 9.1 SP0/SP1) and allows the attacker to execute arbitrary code with the privileges of the service. The code is written in Ruby and is structured as a standard Metasploit module, with all exploit logic contained in a single file.
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.