CVE-2013-2346
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 · uneditedUnspecified 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-1870.
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 · high confidenceHP Storage Data Protector 6.2X contains an unspecified vulnerability (ZDI-CAN-1870) that allows remote attackers to execute arbitrary code or cause a denial of service. The exact attack vector and technical details are not public, but the CVSS 10 score indicates a critical flaw easily exploitable over the network.
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= 6.20= 6.21CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HP Storage Data Protector is installedCheck your systems for the presence of HP Storage Data Protector software. On Windows, look in Add/Remove Programs or check for the installation directory. On Unix/Linux, check for /opt/omnisselect or /opt/hp/dataprotector and related directories.Affected if The software is present on the system
-
Identify the installed versionLocate the version information for the HP Storage Data Protector installation. This is typically available through the product's graphical or command-line interface, or check installation logs and version files within the product directory.Affected if The installed version is exactly 6.20 or exactly 6.21
-
Verify the vulnerable versionsCompare your identified version against the affected ranges: version 6.20 and version 6.21. Any other version (earlier or later) is not affected by this specific CVE.Affected if The version matches 6.20 or 6.21 exactly
-
Assess network exposureDetermine if the HP Storage Data Protector service is accessible over the network. Check firewall rules, listening ports, and whether the management interface is exposed to untrusted networks.Affected if The service is network-accessible from untrusted or external networks
You are affected if HP Storage Data Protector version 6.20 or 6.21 is installed and the service is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches from HP immediately when available. In the interim, isolate the Storage Data Protector systems behind firewalls, restrict network access to only authorized management hosts, and monitor for indicators of compromise.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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