CVE-2011-1730
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 · uneditedStack-based buffer overflow in OmniInet.exe in the Backup Client Service in HP OpenView Storage Data Protector 6.00, 6.10, and 6.11 allows remote attackers to execute arbitrary code via a malformed EXEC_SCRIPT message.
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 confidenceStack-based buffer overflow in OmniInet.exe in HP OpenView Storage Data Protector allows remote attackers to execute arbitrary code via a malformed EXEC_SCRIPT message to the Backup Client Service.
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.00= 6.10= 6.11CVSS 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 OpenView Storage Data Protector is installedLook for the product in installed programs (Windows Add/Remove Programs) or check for the installation directory typically under C:\Program Files\HP\Data Protector or /opt/omniAffected if The product is present on the system
-
Identify the installed versionCheck the product version through the installer, or look for version information in the installation directory, or run 'omn version' from the bin directory if availableAffected if The installed version is 6.00, 6.10, or 6.11 exactly as listed in affected versions
-
Verify OmniInet.exe is presentCheck for OmniInet.exe in the installation bin directory (commonly C:\Program Files\HP\Data Protector\bin\ or /opt/omni/bin/)Affected if OmniInet.exe exists in the Data Protector installation directory
-
Check if the Backup Client Service is runningOpen Windows Services console and look for 'HP OpenView Storage Data Protector' or 'OmniInet' service, or run 'omnisv -status' if the command-line tool is availableAffected if The Backup Client Service (OmniInet) is running or enabled
-
Assess network exposure of the serviceCheck if port 5555 (default OmniInet port) or other Data Protector ports are listening and accessible from the network using netstat -an or a port scannerAffected if The OmniInet service is listening on a network-accessible port and reachable from untrusted networks
You are affected if HP OpenView Storage Data Protector version 6.00, 6.10, or 6.11 is installed AND the OmniInet.exe Backup Client Service is running and 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 HP security patches for this vulnerability; if unavailable, disable or restrict network access to the Backup Client Service (OmniInet.exe) and implement network segmentation to limit exposure.
- Consultation8.0 h
- Implementation4.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 $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1730 — 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-2011-1730 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