VERITAS Backup Exec Server (beserver.exe) versions 9.0 through 10.0 for Windows expose an RPC interface on TCP port 6106 that allows remote, unauthenticated attackers to modify the Windows registry by invoking specific methods. The vulnerability arises from insufficient authentication and authorization checks on the RPC interface, permitting arbitrary registry modifications.
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 auxiliary module (modules/auxiliary/admin/backupexec/registry.rb) targeting a remote registry access vulnerability (CVE-2005-0771) in the Veritas Backup Exec Windows Server RPC service. The module allows an attacker with network access to port 6106/tcp on a vulnerable Backup Exec server to remotely read, write, and enumerate Windows registry keys. The module provides two main actions: dumping system information (such as OS version, registered owner, CPU, and current user) and setting a custom logon notice on the target system. The exploit leverages the DCERPC interface (UUID 93841fd0-16ce-11ce-850d-02608c44967b) to communicate with the service. The code is written in Ruby and is designed to be run within the Metasploit Framework. The module is operational and provides real impact (registry manipulation and information disclosure) but does not include a customizable payload beyond the provided actions.
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.