CVE-2013-2333 is an unspecified vulnerability in HP Storage Data Protector versions 6.20, 6.21, 7.00, and 7.01. The vulnerability allows remote attackers to execute arbitrary code via unknown vectors. The issue is referenced as ZDI-CAN-1680, but technical details about the vulnerable component or function are not publicly disclosed.
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 module (hp_dataprotector_crs.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2013-2333) in the HP Data Protector Cell Request Service (crs.exe) on Windows. The exploit targets versions 6.20 build 370 and 7.00 build 72, specifically on Windows XP SP3. The module works by first connecting to the Data Protector service (typically on TCP port 5555) to fingerprint the version and discover the random port used by the CRS service. It then sends a series of crafted packets, culminating in a malicious packet with opcode 211 that triggers the buffer overflow and executes a user-supplied Metasploit payload. The exploit is weaponized, allowing for arbitrary code execution with the privileges of the CRS service, and is configurable to deliver various payloads (e.g., reverse shell, Meterpreter). The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to use within 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.