dbcve.org
Storage Data ProtectorApplication · Hp

CVE-2013-2329

HIGH · 10.0 CVSS v2.0 Published 2013-06-06
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 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.20, 6.21, 7.00, and 7.01 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1637.

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 versions 6.20, 6.21, 7.00, and 7.01 contain an unspecified vulnerability allowing remote attackers to execute arbitrary code via unknown vectors. The vulnerability is rated critical severity (CVSS 10) and was disclosed through the Zero Day Initiative (ZDI-CAN-1637).

MitigationUpgrade HP Storage Data Protector to the vendor-supplied patched version. If patching is not immediately possible, isolate affected systems from untrusted networks and monitor for indicators of compromise.

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= 7.00= 7.01

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. Confirm HP Storage Data Protector is installed
    Check system for presence of HP Storage Data Protector software using system inventory tools, installed programs list, or by searching for Data Protector directories on the system.
    Affected if HP Storage Data Protector is found on the system
  2. Determine installed version
    Locate and read the version information for HP Storage Data Protector. Common methods include checking the software's About dialog, reading version files in the installation directory, or querying the installed package through system tools.
    Affected if The installed version cannot be determined or is not clearly identified
  3. Compare version against affected releases
    Match the identified version number exactly to 6.20, 6.21, 7.00, or 7.01.
    Affected if The installed version exactly matches 6.20, 6.21, 7.00, or 7.01

A system is affected if HP Storage Data Protector is installed and the exact version is one of the following: 6.20, 6.21, 7.00, or 7.01.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade HP Storage Data Protector to the vendor-supplied patched version. If patching is not immediately possible, isolate affected systems from untrusted networks and monitor for indicators of compromise.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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