Intelligent Management Center User Access ManagerApplication · Hp

CVE-2012-5211

HIGH · 7.5 CVSS v2.0 Published 2013-03-09
Fix available
A fix is available. Upgrade to after 5.1 or later.
See remediation →
84/100
Remediation priority · High
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
Unspecified vulnerability in HP Intelligent Management Center (iMC) User Access Manager (UAM) before 5.2 E0402 allows remote attackers to obtain sensitive information, modify data, or cause a denial of service via unknown vectors, aka ZDI-CAN-1643.

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

HP Intelligent Management Center User Access Manager (UAM) before version 5.2 E0402 contains an unspecified vulnerability (ZDI-CAN-1643) that allows remote attackers to potentially obtain sensitive information, modify data, or cause denial of service. The vulnerability is network-exploitable with CVSS 7.5 indicating high exploitability, though the exact technical vector is not disclosed.

MitigationApply HP iMC UAM version 5.2 E0402 or later to address this vulnerability. If immediate patching is not feasible, restrict network access to the iMC management interface via firewall or VPN to limit exposure to untrusted networks.

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
Intelligent Management Center User Access ManagerApplication
Affected:<= 5.1

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 iMC UAM is installed
    Check the system for HP Intelligent Management Center User Access Manager by looking for the iMC installation directory (typically under C:\hp\iMC or C:\Program Files\HP\iMC) and locate the UAM component subdirectory
    Affected if HP iMC UAM software is present on the system
  2. Determine UAM component version
    Locate the UAM version file or check the iMC console for the User Access Manager component version information. The version is typically displayed in the iMC management console under System > Components or in a version.txt file within the UAM installation folder
    Affected if The installed UAM version is 5.1 or earlier, or if the version cannot be determined but the overall iMC build is before E0402
  3. Confirm iMC platform version
    Check the overall HP iMC platform version by logging into the iMC management console or inspecting the iMC installation metadata
    Affected if The iMC platform version is 5.1 or earlier, indicating the entire deployment includes the vulnerable UAM component
  4. Verify UAM service is running
    Check if the UAM service is running by looking for the UAM-related Windows service (typically named 'HP iMC UAM' or similar) in Windows Services or by querying running processes for UAM-related executables
    Affected if The UAM service is actively running and accessible
  5. Assess network exposure
    Review firewall rules and network access controls to determine if the iMC management interface (typically ports 8080, 8443, or 80/443 for web console) is exposed to untrusted networks
    Affected if The iMC UAM web interface is accessible from networks outside the trusted internal environment

The environment is affected if HP Intelligent Management Center with UAM component version 5.1 or earlier is installed and the UAM service is running and network-accessible.

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
Upgrade available Upgrade to a release after 5.1
Interim mitigation

Apply HP iMC UAM version 5.2 E0402 or later to address this vulnerability. If immediate patching is not feasible, restrict network access to the iMC management interface via firewall or VPN to limit exposure to untrusted networks.

Fix this in Intelligent Management Center User Access Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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