CVE-2011-1732
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 stutil 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 the OmniInet.exe Backup Client Service of HP OpenView Storage Data Protector versions 6.00, 6.10, and 6.11 allows remote attackers to execute arbitrary code via a malformed stutil message. The overflow occurs on the stack, enabling complete remote code execution with elevated privileges.
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 installedCheck for the presence of the HP OpenView Storage Data Protector installation directory, typically found under C:\Program Files\HP\Data Protector or /opt/HP/Data Protector on Unix systems. Look for the Data Protector client or server executables.Affected if The product is installed on the system.
-
Verify the installed version numberLocate the version information for the Data Protector installation. This can typically be found in the program files directory, in an about dialog, or by querying the installed software inventory on the system. Compare the version to 6.00, 6.10, or 6.11.Affected if The installed version is 6.00, 6.10, or 6.11 exactly.
-
Confirm the OmniInet.exe service exists and is runningCheck the running processes on the system for omniinet.exe or check the Windows Services list for the HP OpenView Storage Data Protector Inet service. On Unix systems, check running processes for omniinet.Affected if The OmniInet.exe process is running on the system.
-
Verify the stutil protocol listener is activeCheck if the Backup Client Service is listening on the network. The OmniInet service typically listens on TCP port 5555 (or configurable ports) for stutil protocol communications. Use netstat or similar network tooling to check for listening ports associated with the Data Protector service.Affected if The service is listening on a network port and accessible over the network.
-
Determine network exposure of the serviceReview firewall rules and network configuration to determine if the Backup Client Service port is accessible from untrusted networks. Check if the service is bound to interfaces accessible from outside the local network.Affected if The service port is accessible from untrusted network segments.
A system is affected if HP OpenView Storage Data Protector version 6.00, 6.10, or 6.11 is installed with the OmniInet.exe service running and exposed to 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.
dbcve · scopedUpgrade HP OpenView Storage Data Protector to a patched version or apply vendor-supplied security updates. If immediate patching is not possible, restrict network access to the Backup Client Service port and disable stutil protocol handling at the network perimeter.
HP OpenView Storage Data Protector 6.20 or later (contact HP for exact fixed version)
- 1. Visit the official HP Support website at h20000.www2.hp.com to locate the Security Bulletin for CVE-2011-1732
- 2. Download the applicable patch or upgrade package for HP OpenView Storage Data Protector
- 3. Review the patch release notes to confirm it addresses the OmniInet.exe stack-based buffer overflow (CVE-2011-1732)
- 4. Apply the patch or upgrade following HP's standard installation procedures
- 5. Verify the installation by checking that OmniInet.exe version has been updated
- 6. Test that Backup Client Service functionality remains operational after the update
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2011-1732 — 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-1732 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