dbcve.org
Intelligent Management CenterApplication · Hp

CVE-2012-5209

HIGH · 10.0 CVSS v2.0 Published 2013-03-09
Fix available
A fix is available. Upgrade to after 5.1 or later.
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
Unspecified vulnerability in HP Intelligent Management Center (iMC) and Intelligent Management Center for Automated Network Manager (ANM) before 5.2 E0401 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1659.

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 (iMC) and ANM before version 5.2 E0401 contain an unspecified vulnerability allowing remote attackers to execute arbitrary code. The CVSS score of 10 indicates complete compromise with no authentication required. The exact attack vector is not disclosed in available documentation.

MitigationUpgrade HP iMC/ANM to version 5.2 E0401 or later. If immediate patching is not feasible, restrict network access to management interfaces and monitor for indicators of compromise.

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 CenterApplication
Affected:<= 5.1= 5.0= 5.1
Intelligent Management Center For Automated Network 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
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 iMC or ANM installation
    Check for HP Intelligent Management Center or Automated Network Manager in installed programs (Windows: Add/Remove Programs, Linux: rpm -qa or dpkg -l), or look for installation directories such as C:/HP/imc or /opt/hp/imc
    Affected if HP iMC or ANM software is present on the system
  2. Identify installed version
    Locate version information in the installation directory, typically in a version.txt, about dialog, or registry key under HKLM\Software\HP\iMC or HKLM\Software\Hewlett-Packard\ANM on Windows. On Linux, check /opt/hp/imc/etc/appconfig.ini or similar configuration files
    Affected if The discovered version is 5.0, 5.1, or any version <= 5.1
  3. Verify patch level for version 5.2
    If version 5.2 is found, confirm the exact build or E-pack version - look for E0401 or higher in the version string (for example, 5.2 E0401, 5.2 E0502)
    Affected if Version is 5.2 but the build/E-pack is earlier than E0401
  4. Assess network exposure
    Determine if the iMC/ANM management interfaces are accessible from untrusted networks. Check firewall rules, listening ports (typically 8080, 8443 for web UI), and whether the system is directly internet-facing
    Affected if Management ports are open to untrusted network segments or the internet

The environment is affected if HP iMC or ANM version 5.2 E0401 or later is NOT installed, or if version 5.2 with a build earlier than E0401 is present.

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

Upgrade HP iMC/ANM to version 5.2 E0401 or later. If immediate patching is not feasible, restrict network access to management interfaces and monitor for indicators of compromise.

Recommended fix High confidence

HP Intelligent Management Center 5.2 E0401 or later

  1. Download HP Intelligent Management Center version 5.2 E0401 or later from the official HP support portal
  2. Ensure all prerequisites for version 5.2 are met before upgrading
  3. Back up the current iMC/ANM configuration and database
  4. Stop the iMC/ANM services before initiating the upgrade
  5. Run the installer for version 5.2 E0401 or later
  6. Follow the on-screen installation prompts to complete the upgrade
  7. Restart the iMC/ANM services after installation completes
  8. Verify the upgrade was successful and the web interface is accessible
Caveat Review HP release notes for version 5.2 for any configuration changes or migration requirements before upgrading

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

Fix this in Intelligent Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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