dbcve.org
Data ProtectorApplication · Hp

CVE-2016-2006

CRITICAL · 9.8 CVSS v3.0 Published 2016-04-21
Fix available
A fix is available. Upgrade to 7.03_108 / 8.15 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
HPE Data Protector before 7.03_108, 8.x before 8.15, and 9.x before 9.06 allows remote attackers to execute arbitrary code via unspecified vectors, aka ZDI-CAN-3353.

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 code execution vulnerability (ZDI-CAN-3353) affecting versions 7.x before 7.03_108, 8.x before 8.15, and 9.x before 9.06. The vulnerability is remotely exploitable without authentication and allows arbitrary code execution, indicating a critical flaw in input handling or service logic.

MitigationImmediately upgrade HPE Data Protector to version 7.03_108, 8.15, or 9.06 or later. If immediate patching is not feasible, restrict network access to Data Protector services and implement network segmentation to limit exposure.

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:>= 7.0, < 7.03_108>= 8.0, < 8.15>= 9.0, < 9.06

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. Verify HPE Data Protector is installed
    Check for the presence of HP Data Protector installation directory. On Windows, look in C:\Program Files\HP\Data Protector\ or C:\Program Files\Hewlett-Packard\Data Protector\. On Unix/Linux, check /opt/HP/dataprotector/ or /opt/hp/dataprotector/. Also check running processes for 'omni' or 'dataprotector' related services.
    Affected if HPE Data Protector software is found on the system
  2. Determine installed Data Protector version
    Locate the version file in the installation directory. On Windows, check version.ini or VERSION.txt in the bin directory. On Unix/Linux, run 'omniversion' if available, or check /opt/HP/dataprotector/etc/omni(version) for version strings.
    Affected if Installed version falls within these ranges: 7.0 to <7.03_108, 8.0 to <8.15, or 9.0 to <9.06
  3. Check if Data Protector services are running and listening
    Run 'netstat -an' or 'ss -tlnp' to identify listening ports. HPE Data Protector typically uses ports 5555 (OMNI), 5556, 7112, and 7114. Identify which ports the Data Protector services are bound to.
    Affected if Data Protector services are listening on network interfaces accessible from untrusted networks
  4. Verify service exposure and authentication configuration
    Review Data Protector configuration files (typically in etc/ directory) to confirm whether the service requires authentication and which network interfaces it binds to. Check omnirc or omnicfg settings.
    Affected if Service is bound to 0.0.0.0 or accessible externally and authentication is not enforced for the vulnerable component

System is affected if HPE Data Protector is installed with version 7.x before 7.03_108, 8.x before 8.15, or 9.x before 9.06, and the service is running and network-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 7.03_108 / 8.15 / 9.06 or later
Fixed in 7.03_1088.159.06
Interim mitigation

Immediately upgrade HPE Data Protector to version 7.03_108, 8.15, or 9.06 or later. If immediate patching is not feasible, restrict network access to Data Protector services and implement network segmentation to limit exposure.

Recommended fix High confidence

Upgrade to Data Protector 7.03_108 (minimum for 7.x), 8.15 (minimum for 8.x), or 9.06 (minimum for 9.x)

  1. 1. Identify the currently installed HPE Data Protector version by checking the product console or running 'omreport' or 'omn versions' command
  2. 2. Determine which version branch (7.x, 8.x, or 9.x) is currently in use
  3. 3. Download the appropriate fixed version from HPE support portal: 7.03_108 for 7.x branch, 8.15 for 8.x branch, or 9.06 for 9.x branch
  4. 4. Stop all Data Protector services on all cells and clients before upgrading
  5. 5. Backup the Data Protector configuration and database using 'omnbackup' command
  6. 6. Install the upgrade on the Cell Manager first, following HPE installation documentation
  7. 7. Upgrade all other components (clients, media servers) after Cell Manager upgrade
  8. 8. Verify the upgrade by checking version with 'omn versions' or 'omreport'
Caveat Review HPE release notes for specific version for any configuration or compatibility changes before upgrading

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

Fix this in Data Protector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-2006 — 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-2016-2006 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