CVE-2013-2347
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 · uneditedThe Backup Client Service (OmniInet.exe) in HP Storage Data Protector 6.2X allows remote attackers to execute arbitrary commands or cause a denial of service via a crafted EXEC_BAR packet to TCP port 5555, aka ZDI-CAN-1885.
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 a critical vulnerability in the Backup Client Service (OmniInet.exe) listening on TCP port 5555. Attackers can send a specially crafted EXEC_BAR packet to achieve remote code execution or cause a denial of service on the affected system.
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.
-
Determine HP Storage Data Protector versionCheck the installed version of HP Storage Data Protector through the Windows Add/Remove Programs list, the program files directory, or by running 'omniversion' if available from the installationAffected if The installed version equals 6.20 or 6.21
-
Verify OmniInet.exe process is runningOpen Task Manager or use the command 'tasklist /FI "IMAGENAME eq OmniInet.exe"' to check if the OmniInet.exe process is activeAffected if The OmniInet.exe process is running on the system
-
Confirm TCP port 5555 is listeningRun 'netstat -an | findstr :5555' or use a port scanner tool to check if TCP port 5555 is in a LISTENING stateAffected if Port 5555 is open and accepting connections
-
Check network exposure of port 5555Use 'netstat -an' with the local address information to determine which network interfaces port 5555 is bound to, or scan the port from an external system to confirm accessibilityAffected if Port 5555 is bound to 0.0.0.0 or an externally accessible IP address, making it reachable from untrusted networks
The system is affected if HP Storage Data Protector version 6.20 or 6.21 is installed AND the OmniInet.exe service is running with TCP port 5555 exposed on the network.
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 dataRestrict network access to TCP port 5555 to trusted hosts only, apply the vendor patch for HP Storage Data Protector, or disable the OmniInet service if the backup client functionality is not required.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2347 — 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-2347 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