CVE-2011-1735
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 bm 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 (Backup Client Service) in HP OpenView Storage Data Protector allows remote attackers to execute arbitrary code via malformed bm messages. The vulnerability exists in versions 6.00, 6.10, and 6.11 of the software.
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.
-
Verify HP OpenView Storage Data Protector installationLocate the installation directory for HP OpenView Storage Data Protector, typically found in C:\Program Files\HP\Data Protector or similar paths. Check for the presence of the OmniInet.exe binary.Affected if The software is not installed or OmniInet.exe is not present on the system, the vulnerability does not apply.
-
Determine installed software versionRight-click on OmniInet.exe in the installation directory, select Properties, and check the Version tab. Alternatively, check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\HP\Data Protector\InstalledVersion or use the 'hpdpversion' command if available.Affected if The installed version is exactly 6.00, 6.10, or 6.11, the system is running a vulnerable version.
-
Confirm OmniInet service is runningOpen Services console (services.msc) and locate the 'HP OpenView Storage Data Protector' or 'OmniInet' service. Check its status. Alternatively, run 'sc query omniinet' from command prompt.Affected if The service is not running, the immediate risk from remote exploitation is reduced, though local privilege escalation could still be a concern.
-
Check if OmniInet service is listening on network portsUse netstat command: 'netstat -an | findstr LISTENING' or run 'netstat -abn' and look for entries associated with omniinet.exe. Also check open ports with 'netsh firewall show portopening'.Affected if The service is listening on network ports and the version is 6.00, 6.10, or 6.11, the system is vulnerable to remote exploitation via malformed bm messages.
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 network connections.
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 dataUpdate HP OpenView Storage Data Protector to a patched version or apply vendor-supplied security patches to address the buffer overflow in OmniInet.exe.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1735 — 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-1735 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