dbcve.org
Endpoint Admission DefenseApplication · Hp

CVE-2011-1867

HIGH · 10.0 CVSS v2.0 Published 2011-07-11
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 iNodeMngChecker.exe in the User Access Manager (UAM) 5.0 before SP1 E0101P03 and Endpoint Admission Defense (EAD) 5.0 before SP1 E0101P03 components in HP Intelligent Management Center (aka iNode Management Center) allows remote attackers to execute arbitrary code via a 0x0A0BF007 packet.

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 · moderate confidence

Stack-based buffer overflow in the iNodeMngChecker.exe component of HP Intelligent Management Center allows remote attackers to execute arbitrary code via a specially crafted 0x0A0BF007 packet. The vulnerability affects User Access Manager (UAM) 5.0 and Endpoint Admission Defense (EAD) 5.0 versions before SP1 E0101P03.

MitigationApply HP service pack SP1 E0101P03 or later to both UAM and EAD components. If patching is not immediately possible, restrict network access to the iNode Management Center services to trusted internal IPs only.

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
Endpoint Admission DefenseApplication
Affected:= 5.0
Intelligent Management CenterApplication
Affected:all versions
User Access ManagerApplication
Affected:= 5.0

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. Identify if HP Intelligent Management Center or its components are installed
    Look for HP iNode Management Center, User Access Manager (UAM), or Endpoint Admission Defense (EAD) installation directories or check Add/Remove Programs for HP iNode-related software
    Affected if Any of these HP management components are installed
  2. Check the installed version of User Access Manager
    Inspect the UAM version information through the application or its installation directory
    Affected if Version is 5.0 (exact match to affected version)
  3. Check the installed version of Endpoint Admission Defense
    Inspect the EAD version information through the application or its installation directory
    Affected if Version is 5.0 and the service pack level is before SP1 E0101P03
  4. Check if iNodeMngChecker.exe is running
    Look for the iNodeMngChecker.exe process in running processes on the system
    Affected if The iNodeMngChecker.exe process is active (this is the vulnerable component)
  5. Verify the service pack level on UAM or EAD
    Check the installed service pack or patch level of the UAM or EAD installation
    Affected if Service pack is not SP1 E0101P03 or later (vulnerable if below this level)

Your environment is affected if HP Intelligent Management Center, User Access Manager 5.0, or Endpoint Admission Defense 5.0 is installed with the iNodeMngChecker.exe component running and the service pack is below SP1 E0101P03.

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 HP service pack SP1 E0101P03 or later to both UAM and EAD components. If patching is not immediately possible, restrict network access to the iNode Management Center services to trusted internal IPs only.

Recommended fix High confidence

HP Intelligent Management Center / UAM / EAD SP1 E0101P03 or later

  1. 1. Identify the exact version of HP Intelligent Management Center, User Access Manager (UAM), or Endpoint Admission Defense (EAD) currently installed
  2. 2. If the version is earlier than SP1 E0101P03, obtain the SP1 E0101P03 patch or later from HP
  3. 3. Apply the SP1 E0101P03 patch following HP's standard patch installation procedures
  4. 4. Verify the installation was successful and the iNodeMngChecker.exe version reflects the patched release

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

Fix this in Endpoint Admission Defense Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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