Loading vulnerability…
A vulnerability in HP OmniBackII version A.03.50 and earlier on HP-UX 11.x and prior allows attackers to gain unauthorized access to an OmniBack client. The flaw is related to insufficient access controls or authentication mechanisms in the OmniBack client service, enabling attackers to bypass intended security restrictions.
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 (2 hidden).
This repository contains a single Metasploit module: 'openview_omniback_exec.rb', which exploits a command execution vulnerability (CVE-2001-0311) in HP OpenView OmniBack II (also known as HP Data Protector). The exploit targets the service running on TCP port 5555 and allows remote attackers to execute arbitrary commands on both Unix and Windows systems. On Unix, the exploit leverages /bin/sh for command execution, while on Windows, it attempts to use perl.exe. The module includes both a check and exploit method, and supports Metasploit's cmd payloads. The code is operational and can be used to gain remote command execution on vulnerable systems, subject to payload and command length limitations (especially on Windows). The repository is structured as a single Ruby file compatible with 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.