CVE-2013-2350
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-1897.
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 confidenceHP Storage Data Protector 6.2X contains an unspecified vulnerability (ZDI-CAN-1897) with a CVSS score of 10, allowing remote attackers to execute arbitrary code or cause denial of service without authentication. The exact attack vector and technical details were not disclosed at time of publication, characteristic of a zero-day disclosure coordinated through ZDI.
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.
-
Identify installed HP Storage Data Protector versionLocate the Data Protector installation directory and check version information via the product'sAbout dialog, version file, or command-line utility (omscrv -version or similar).Affected if The installed version is exactly 6.20 or exactly 6.21.
-
Verify Data Protector service is network-facingReview firewall rules, network configurations, and listening services to determine if the Data Protector service ports (typically 5555 for OMNIbus, 5556 for Data Protector) are exposed to untrusted networks.Affected if Data Protector ports are accessible from networks outside the trusted administrative zone.
-
Check for unauthorized access indicatorsReview Data Protector audit logs, event logs, and security logs for authentication failures, unexpected commands, or anomalous client connections around the publication date of this vulnerability.Affected if Any suspicious authentication events, unknown client connections, or unexpected commands appear in logs.
-
Inspect running processes and scheduled tasksExamine active processes and scheduled jobs on the Data Protector server for unauthorized executables, unexpected scripts, or processes spawned by the Data Protector service account.Affected if Unexpected processes or scheduled tasks exist that were not authorized by administrators.
A system is affected if HP Storage Data Protector version 6.20 or 6.21 is installed and the service is network-accessible, making it vulnerable to remote unauthenticated attacks.
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 HP patches for Storage Data Protector 6.2X as soon as available; meanwhile, restrict network access to Data Protector services, isolate the system behind firewalls, and monitor for indicators of compromise.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-2350 — 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-2350 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