dbcve.org
Openview Storage Data ProtectorApplication · Hp

CVE-2011-1866

HIGH · 10.0 CVSS v2.0 Published 2011-07-01
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
Public exploit 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
Buffer overflow in omniinet.exe in the inet service in HP OpenView Storage Data Protector 6.00 through 6.20 allows remote attackers to execute arbitrary code via a crafted request, related to the EXEC_CMD functionality.

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

Buffer overflow in omniinet.exe within the inet service of HP OpenView Storage Data Protector versions 6.00-6.20 allows remote unauthenticated attackers to execute arbitrary code via specially crafted requests to the EXEC_CMD functionality.

MitigationApply vendor patches for HP OpenView Storage Data Protector; if patches are unavailable, disable the inet service or restrict network access to the affected port.

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= 6.20

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. Confirm HP OpenView Storage Data Protector installation
    Locate the Data Protector installation directory and identify the installed version using the installer, registry key, or version information in the program files (commonly in C:\Program Files\HP\Data Protector or /opt/HP/Data Protector on Unix)
    Affected if The software is installed and the version is 6.00, 6.10, 6.11, or 6.20
  2. Identify inet service process
    Check if the omniinet.exe process is running (on Windows: tasklist | findstr omniinet.exe; on Unix: ps -ef | grep omniinet)
    Affected if The omniinet.exe process is running and listening for network connections
  3. Verify version matches affected range
    Compare your installed Data Protector version to the affected list: 6.00, 6.10, 6.11, or 6.20
    Affected if The installed version is exactly 6.00, 6.10, 6.11, or 6.20
  4. Check inet service network exposure
    Identify the port the inet service is listening on (default 5555) and verify network accessibility (netstat -an | grep 5555 or equivalent)
    Affected if The inet service port is exposed to untrusted network segments

You are affected if HP OpenView Storage Data Protector versions 6.00, 6.10, 6.11, or 6.20 are installed AND the inet service (omniinet.exe) is running and network-accessible, allowing remote attackers to reach the EXEC_CMD functionality.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for HP OpenView Storage Data Protector; if patches are unavailable, disable the inet service or restrict network access to the affected port.

Recommended fix Moderate confidence

HP Data Protector 6.20 with corresponding security patch (HPESB2011013) or later fixed release

  1. 1. Identify the currently installed HP Data Protector version by checking the omniinet.exe file version or using the 'omnversion' command-line utility.
  2. 2. Visit the official HP support portal (support.hp.com) and search for security bulletin HPESB2011013 or CVE-2011-1866.
  3. 3. Download and apply the appropriate patch or upgrade to a fixed version as specified in the HP security bulletin.
  4. 4. After patching, restart the Data Protector inet service (omniinet) to ensure the fix takes effect.
  5. 5. Verify the patch was applied successfully by checking the version again and confirming the inet service is running without errors.
Caveat Review HP release notes for the patch for any configuration changes or compatibility considerations; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-1866 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