Openview Storage Data ProtectorApplication · Hp

CVE-2011-1728

HIGH · 10.0 CVSS v2.0 Published 2011-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Stack-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_BAR 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 confidence

A stack-based buffer overflow exists in OmniInet.exe, the Backup Client Service component of HP OpenView Storage Data Protector versions 6.00, 6.10, and 6.11. The vulnerability is triggered by sending a malformed EXEC_BAR message to the service, allowing remote attackers to overwrite stack memory and execute arbitrary code with the privileges of the affected service.

MitigationApply vendor-supplied patches for HP Data Protector or upgrade to an unaffected version. If patches are unavailable, restrict network access to the Backup Client Service port and consider disabling the service if not 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
Openview Storage Data ProtectorApplication
Affected:= 6.00= 6.10= 6.11

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify HP Data Protector installation
    Check for the presence of the HP Data Protector installation directory, typically found under C:\Program Files\HP\Data Protector or similar paths depending on the operating system.
    Affected if HP Data Protector software is not installed on the system.
  2. Identify the installed version
    Locate the version information for HP Data Protector. Check installation logs, the product GUI, or registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\HP\Data Protector for the version value.
    Affected if The installed version matches 6.00, 6.10, or 6.11 exactly.
  3. Confirm OmniInet.exe is present
    Locate the OmniInet.exe executable in the Data Protector installation directory, typically in the bin or etc subfolder.
    Affected if OmniInet.exe exists in the Data Protector installation path.
  4. Check if Backup Client Service is running
    Verify the OmniInet service status using the Windows Services console (services.msc) or the command 'sc query OmniInet' or look for the process listening on the Data Protector client port.
    Affected if The OmniInet service is running or the process is active on the system.
  5. Assess network exposure of the service
    Determine if the OmniInet service port (default TCP 5555 for Data Protector client) is listening on network interfaces and accessible from untrusted networks. Use 'netstat -an' or port scanning tools to identify exposed listening ports.
    Affected if The service port is bound to a network-facing interface and accessible from outside the local network.

A system is affected if HP Data Protector versions 6.00, 6.10, or 6.11 are installed with the OmniInet.exe (Backup Client Service) running and exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches for HP Data Protector or upgrade to an unaffected version. If patches are unavailable, restrict network access to the Backup Client Service port and consider disabling the service if not required.

Fix this in Openview Storage Data Protector Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1728 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1728 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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