CVE-2014-2623

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 89.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 89%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 89%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Unspecified vulnerability in HP Storage Data Protector 8.x allows remote attackers to execute arbitrary code via unknown vectors.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
85(Track)
EG Risk 85/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation89% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
89%
EPSS %ILE
100%
KEV
Not listed

Published

July 18, 2014

Last Modified

May 6, 2026

References (14)

Data Freshness Timeline

(refreshed 2× in last 7d / 4× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 23:44 UTCEPSS rescore
  2. 2026-08-16 02:09 UTCEPSS rescore
  3. 2026-07-28 15:31 UTCEPSS rescore
  4. 2026-07-26 13:50 UTCEG score recompute▲ 10.00
  5. 2026-07-23 01:18 UTCGHSA enrichment
  6. 2026-07-23 01:17 UTCGHSA enrichment
  7. 2026-07-23 01:15 UTCGHSA enrichment
  8. 2026-07-23 01:14 UTCGHSA enrichment
  9. 2026-07-23 01:12 UTCEG score recompute▼ 9.00
  10. 2026-07-23 00:16 UTCEG score recompute
  11. 2026-07-22 21:54 UTCEG score recompute
  12. 2026-07-22 14:04 UTCEPSS rescore
  13. 2026-07-20 17:03 UTCEPSS rescore
  14. 2026-07-20 17:03 UTCEPSS rescore
  15. 2026-07-19 02:25 UTCEPSS rescore
  16. 2026-07-15 16:54 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-09 19:05 UTCEPSS rescore
  19. 2026-07-04 06:27 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
Show 36 more
  1. 2026-06-22 14:22 UTCEPSS rescore
  2. 2026-06-22 14:22 UTCEPSS rescore
  3. 2026-06-15 17:44 UTCEPSS rescore
  4. 2026-06-14 23:14 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-12 23:08 UTCEPSS rescore
  7. 2026-06-10 22:15 UTCEPSS rescore
  8. 2026-06-10 13:18 UTCEPSS rescore
  9. 2026-06-07 15:22 UTCEPSS rescore
  10. 2026-06-06 13:45 UTCEPSS rescore
  11. 2026-06-06 13:45 UTCEPSS rescore
  12. 2026-06-04 13:09 UTCEPSS rescore
  13. 2026-06-04 13:09 UTCEPSS rescore
  14. 2026-06-02 20:10 UTCEPSS rescore
  15. 2026-06-02 20:10 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-05-31 22:28 UTCEPSS rescore
  19. 2026-05-31 22:28 UTCEPSS rescore
  20. 2026-05-31 00:14 UTCEPSS rescore
  21. 2026-05-31 00:14 UTCEPSS rescore
  22. 2026-05-28 17:56 UTCEG score recompute
  23. 2026-05-28 17:56 UTCGHSA enrichment
  24. 2026-05-28 13:42 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-26 13:41 UTCEPSS rescore
  28. 2026-05-26 13:41 UTCEPSS rescore
  29. 2026-05-26 07:16 UTCEPSS rescore
  30. 2026-05-26 07:16 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 11:21 UTCEPSS rescore
  34. 2026-05-20 11:21 UTCEPSS rescore
  35. 2026-05-18 21:29 UTCEPSS rescore
  36. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-36304✓ verified
    First seen Mar 6, 2015

    HP Data Protector 8.10 - Remote Command Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-35961✓ verified
    First seen Jan 30, 2015

    HP Data Protector 8.x - Remote Command Execution

    Open source ↗
  • Metasploitexploit/windows/misc/hp_dataprotector_cmd_exec✓ verified
    First seen Nov 2, 2014

    HP Data Protector 8.10 Remote Command Execution

    Open source ↗
  • Exploit-DBEDB-34066✓ verified
    First seen Jul 14, 2014

    HP Data Protector Manager 8.10 - Remote Command Execution

    Open source ↗

Frequently asked(4)

What is CVE-2014-2623?
CVE-2014-2623 is a high vulnerability published on July 18, 2014. Unspecified vulnerability in HP Storage Data Protector 8.x allows remote attackers to execute arbitrary code via unknown vectors.
When was CVE-2014-2623 disclosed?
CVE-2014-2623 was first published in the National Vulnerability Database on July 18, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-2623 actively exploited?
CVE-2014-2623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 89% probability of exploitation in the next 30 days, which ranks it in the top 0.2% of all scored CVEs.
How do I remediate CVE-2014-2623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-2623, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2014-2623

Explore →

Is Your Infrastructure Affected by CVE-2014-2623?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs