CVE-2016-2004 — Data Protector
CRITICALCVE-2016-2004 is a critical-severity (CVSS 9.8) Missing Authentication vulnerability in hp data protector. 6 public exploit references exist, so weaponization risk is real. A fix is available — see the affected versions and patch details below.
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.…
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2016-2004 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Description
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.
Affected Products
data protectorhpResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
HP Data Protector A.09.00 - Arbitrary Command Execution
by Ian Lovering · May 26, 2016
HP Data Protector A.09.00 - Encrypted Communications Arbitrary Command Execution (Metasploit)
by Ian Lovering · May 31, 2016
Detection & mitigation playbook
Vendor / applianceDetect
Inventory every hp data protector deployment and check each version against the affected-products list above.
Fix
Apply the hp data protector security patch or hotfix for CVE-2016-2004 on the affected version, following the vendor advisory for your exact build.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2016-2004 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.