dbcve.org
Storage Data ProtectorApplication · Hp

CVE-2013-6194

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
High EPSS Public exploit 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-1905.

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

Critical remote code execution vulnerability in HP Storage Data Protector 6.2X allowing remote attackers to execute arbitrary code or cause denial of service via unspecified attack vectors (ZDI-CAN-1905). The vulnerability is remotely exploitable with CVSS 10.0 indicating complete system compromise potential.

MitigationApply HP security patches for Storage Data Protector 6.2X. If patches unavailable, implement network segmentation to restrict access to Data Protector services and deploy compensating controls such as firewall rules limiting exposure to trusted networks only.

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. Identify if HP Storage Data Protector is installed
    Check for Data Protector installation directories (commonly C:\Program Files\HP\Data Protector or /opt/HP/Data Protector on Unix), or query installed software listings. On Windows, use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' or check services for 'Data Protector' named services. On Unix, check /opt/HP directory existence and run 'omniversion' command if available.
    Affected if HP Storage Data Protector software is found on the system with versions 6.20 or 6.21
  2. Confirm the exact installed version number
    Locate the version file or use version query commands specific to Data Protector. On Windows, check the program's properties in Add/Remove Programs or examine version info in the bin directory. On Unix, run 'omniversion' or check /opt/HP/Data Protector/version.ini.
    Affected if The installed version is exactly 6.20 or exactly 6.21
  3. Check if Data Protector services are exposed on the network
    Identify listening network services. Run 'netstat -an | findstr LISTENING' on Windows or 'netstat -tulpn' on Unix, looking for default Data Protector ports (typically 5555 for OmniBack, 5556, 5557 for related services). Also check if the 'omni' or 'omniback' services are bound to non-loopback interfaces.
    Affected if Data Protector services are listening on accessible network interfaces (not localhost-only) on any port, indicating remote exploit potential
  4. Verify if the vulnerable service is running
    Check if Data Protector-related processes are active. On Windows, run 'tasklist | findstr -i omni' or check the 'OmniBack' service status via 'sc query omni'. On Unix, run 'ps -ef | grep -i omni' to list running Data Protector processes.
    Affected if The Data Protector service daemon (omnisv, omniback, or related processes) is running and exposed to network access

If HP Storage Data Protector version 6.20 or 6.21 is installed and its services are running and network-accessible, the environment is vulnerable to remote code execution and requires immediate attention.

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 HP security patches for Storage Data Protector 6.2X. If patches unavailable, implement network segmentation to restrict access to Data Protector services and deploy compensating controls such as firewall rules limiting exposure to trusted networks only.

Recommended fix Moderate confidence

HP Storage Data Protector 6.22 or later

  1. 1. Identify the current installed version of HP Storage Data Protector by running 'omnicellinfo' or checking the installation directory.
  2. 2. Download HP Storage Data Protector version 6.22 or later from the HP Support Portal (h20565.www2.hp.com).
  3. 3. Review HP's official security bulletin for CVE-2013-6194 for any specific patch requirements.
  4. 4. Create a full backup of the current Data Protector configuration and database.
  5. 5. Stop all Data Protector services using 'omnisv stop_all'.
  6. 6. Install the updated version following HP's upgrade documentation.
  7. 7. Verify the installation succeeded and services start correctly.
  8. 8. Confirm the vulnerability is resolved by checking the version number.
Caveat Review HP's upgrade guide for potential compatibility issues with existing cell setup and client installations before upgrading

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-6194 — 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-6194 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