dbcve.org
Storage Data ProtectorApplication · Hp

CVE-2013-6195

HIGH · 10.0 CVSS v2.0 Published 2014-01-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unspecified vulnerability in HP Storage Data Protector 6.2X allows remote attackers to execute arbitrary code or cause a denial of service via unknown vectors, aka ZDI-CAN-2008.

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

HP Storage Data Protector 6.2X contains an unspecified vulnerability (ZDI-CAN-2008) that allows remote attackers to execute arbitrary code or cause denial of service. The vulnerability is present in enterprise backup/storage software that typically runs with elevated privileges, making successful exploitation particularly dangerous.

MitigationApply available HP patches for Storage Data Protector 6.2X. If no patch exists, restrict network access to the Data Protector services and isolate the system from untrusted networks, as the CVSS 10 score indicates a critical severity requiring immediate attention.

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
Storage Data ProtectorApplication
Affected:= 6.20= 6.21

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 HP Storage Data Protector is installed
    Check for the product in system registry under HKEY_LOCAL_MACHINE\SOFTWARE\HP\Data Protector, or look for installation directory (typically C:\Program Files\HP\Data Protector or /opt/HP/Data Protector on Unix), or query running processes for 'omni*' processes (omnisv, omniback, etc.)
    Affected if HP Storage Data Protector software is present on the system
  2. Identify installed version
    Read the version from registry key HKEY_LOCAL_MACHINE\SOFTWARE\HP\Data Protector\Version, or check the 'about' information via Data Protector client/console, or inspect version file in installation directory
    Affected if Version equals 6.20 or 6.21 exactly
  3. Confirm Data Protector services are running and exposed
    Check if Data Protector services (omnisv, omniback, or related services) are running via 'services.msc' on Windows or 'ps aux' on Unix; use 'netstat -an' or 'ss -tuln' to check if ports 5555, 5565, or other Data Protector ports are listening
    Affected if Data Protector services are active and listening on network ports, exposing the vulnerable component
  4. Verify the cell server or client component is enabled
    Examine Data Protector configuration files (such as omni.cfg or equivalent in the etc/ directory) to confirm the cell server or remote execution components are enabled; check if 'omnirc' or service configurations allow remote connections
    Affected if Cell server or remote execution features are enabled, allowing network-based exploitation

System is affected if HP Storage Data Protector version 6.20 or 6.21 is installed with network-exposed services or remote execution capabilities enabled.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available HP patches for Storage Data Protector 6.2X. If no patch exists, restrict network access to the Data Protector services and isolate the system from untrusted networks, as the CVSS 10 score indicates a critical severity requiring immediate attention.

Recommended fix Moderate confidence

HP Storage Data Protector 6.40 or later (latest supported version)

  1. 1. Check the HP Security Bulletin (reference h20565.www2.hp.com) for the complete list of affected versions and recommended actions.
  2. 2. Back up all critical data and configuration files for HP Storage Data Protector before performing any upgrade.
  3. 3. Review HP Storage Data Protector upgrade documentation for your current version.
  4. 4. Upgrade HP Storage Data Protector to the fixed release version (6.40 or later) as specified in the HP security bulletin.
  5. 5. After upgrade, verify that the Data Protector services start successfully.
  6. 6. Validate that backup and restore operations function correctly.
  7. 7. Monitor HP support channels for any additional required patches or updates.
Caveat Review HP compatibility matrices for your operating system and application integrations before upgrading; major version upgrades may require configuration adjustments

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

Fix this in Storage Data Protector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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