Loading vulnerability…
HPE Data Protector versions before 7.03_108, 8.x before 8.15, and 9.x before 9.06 are vulnerable to remote code execution due to a lack of authentication on certain vectors. This vulnerability is a result of an incomplete fix for CVE-2014-2623, allowing remote attackers to execute arbitrary code without authentication.
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: 'hp_dataprotector_encrypted_comms.rb', which targets HP Data Protector agents running on Windows systems (Vista or newer) with encrypted control communications enabled. The exploit leverages CVE-2016-2004 to achieve remote code execution by establishing an encrypted (SSL/TLS) channel to the agent (default port 5555), then sending a specially crafted payload that is executed via PowerShell on the target. The payload is generated using Metasploit's cmd_psh_payload, allowing for arbitrary command execution. The module includes a check method to detect vulnerable targets and is operational, providing a customizable payload for post-exploitation. The only fingerprintable endpoint is the TCP port 5555, which is the default for the vulnerable service.
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.