CVE-2013-2348
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-1892.
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-1892) that allows remote attackers to execute arbitrary code or cause denial of service via unknown vectors. The CVSS 10 score indicates trivially exploitable remote code execution with no authentication required.
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 if HP Storage Data Protector is installedCheck for installation directories such as C:\Program Files\HP\Data Protector or /opt/HP/Data Protector. On Windows, also check the Windows Services list for 'HP Data Protector' services.Affected if HP Storage Data Protector version 6.20 or 6.21 is installed
-
Determine the installed versionCheck the version of the installed HP Storage Data Protector. Common locations: Look at the 'omni.exe' version property, check the install directory for version files, or run 'omni.exe -version' if available in the command line tools.Affected if The installed version is exactly 6.20 or exactly 6.21
-
Verify if the Data Protector services are runningCheck if HP Data Protector services are running. On Windows, use Services.msc or 'sc query' to check for services like 'HP Data Protector Inet', 'HP Data Protector', or 'OmniBack' services. On Unix, check with 'ps' for processes like 'omni' or 'omniback'.Affected if The Data Protector services are running on the system with version 6.20 or 6.21
-
Check network accessibility of Data Protector portsDetermine if the Data Protector service ports (commonly TCP 5555 for the INET service) are exposed to the network. Use 'netstat -an' or port scanning tools to check if port 5555 or other Data Protector ports are listening on non-localhost interfaces.Affected if The Data Protector service is listening on accessible network interfaces and the version is 6.20 or 6.21
If HP Storage Data Protector version 6.20 or 6.21 is installed and its services are running and network-accessible, the system is affected by this CVE.
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; if unavailable, restrict network access to the service port and consider upgrading to a patched version.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2348 — 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-2348 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