Skip to content
Fencer Vulns
critical 9.8

CVE-2016-2004 in the critical feed json

HPE Data Protector before 7.03_108, 8.x before 8.15, and 9.x before 9.06 allow remote attackers to execute arbitrary code via unspecified v…

published 2016-04-21 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3112

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
94.3%
EPSS 94.3% chance of exploitation in 30 days, percentile 99.8%
public exploits
3
Metasploit, Exploit-DB, plus a Nuclei check

Summary

HPE Data Protector before 7.03_108, 8.x before 8.15, and 9.x before 9.06 allow remote attackers to execute arbitrary code via unspecified vectors related to lack of authentication. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-2623.

Patch / fix

  • hp data_protector 7.03_108, 8.15, 9.06

Timeline

  1. First public exploit (Metasploit exploit/windows/misc/hp_dataprotector_encrypted_comms)
  2. Published

Exploit prediction

94.25% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/windows/misc/hp_dataprotector_encrypted_comms HP Data Protector Encrypted Communication Remote Command Execution metasploit exploit, normal rank, 2016-04-18
  • EDB-39874 HP Data Protector A.09.00 - Encrypted Communications Arbitrary Command Execution (Metasploit) remote, 2016-05-31
  • EDB-39858 HP Data Protector A.09.00 - Arbitrary Command Execution remote, 2016-05-26
  • Nuclei template HP Data Protector - Arbitrary Command Execution nuclei detection template
  • packetstormsecurity.com http://packetstormsecurity.com/files/137341/HP-Data-Protector-Encrypted-Communication-Remote-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.