dbcve.org
Data ProtectorApplication · Hp

CVE-2017-5807

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-15
Fix available
A fix is available. Upgrade to 8.17 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Remote Arbitrary Code Execution vulnerability in HPE Data Protector version prior to 8.17 and 9.09 was found.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HPE Data Protector contains a remote arbitrary code execution vulnerability allowing unauthenticated attackers to execute code on affected systems. The vulnerability exists in versions prior to 8.17 and 9.09, likely due to insufficient input validation or authentication bypass in the backup/protection service components.

MitigationUpgrade HPE Data Protector to version 8.17 or 9.09 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to Data Protector services and implement additional network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Data ProtectorApplication
Affected:< 8.17= 9.09

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify HPE Data Protector installation
    Locate the HPE Data Protector installation directory and look for version information in the installation folder, or use system inventory tools that enumerate installed HP/HPE software.
    Affected if Data Protector is installed and the version cannot be confirmed as 8.17 or later, or version 9.09 is confirmed.
  2. Retrieve exact Data Protector version
    Check the Data Protector version using the 'omnidbutil -version' command from the Data Protector bin directory, or examine the 'omnicc -version' output if available.
    Affected if The reported version is lower than 8.17, or equals exactly 9.09.
  3. Verify Data Protector services are active
    Check if the Data Protector services (such as HP Data Protector Inet, HP Data Protector Cell Manager, or related services) are running on the system using 'sc query' on Windows or 'service status' commands on Linux.
    Affected if Data Protector services are running and the version check in step 2 confirms an affected version.
  4. Assess network exposure of Data Protector ports
    Review open ports and listening services to determine if Data Protector management or backup ports (commonly TCP 5555, 5556, 5562, or as configured) are exposed to untrusted networks.
    Affected if Data Protector services are listening on accessible network interfaces and the version is in the affected range.

The environment is affected if HPE Data Protector is installed with a version lower than 8.17 or exactly version 9.09, and the Data Protector services are running and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.17 or later
Fixed in 8.17
Interim mitigation

Upgrade HPE Data Protector to version 8.17 or 9.09 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to Data Protector services and implement additional network segmentation.

Recommended fix Moderate confidence

HPE Data Protector 8.17 or 9.09 (or later)

  1. 1. Back up your Data Protector configuration and database before initiating any upgrade
  2. 2. Download HPE Data Protector version 8.17 or version 9.09 (or later) from the HPE Support Center (support.hpe.com)
  3. 3. Review the HPE Data Protector upgrade guide for your current version to ensure compatibility
  4. 4. Stop all Data Protector services on the cell server and clients
  5. 5. Upgrade the Data Protector cell server first, following the HPE installation/upgrade documentation
  6. 6. Upgrade all Data Protector clients to the same version to maintain compatibility
  7. 7. Restart Data Protector services after the upgrade completes
  8. 8. Verify the Data Protector services are running correctly and the version shows as 8.17 or 9.09 or later
Caveat Review HPE compatibility matrices before upgrading; some older OS versions or integrated applications may not be supported in newer Data Protector versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Protector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-5807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-5807 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data