dbcve.org
Intelligent Management Center For Automated Network ManagerApplication · Hp

CVE-2012-5207

HIGH · 9.0 CVSS v2.0 Published 2013-03-09
Fix available
A fix is available. Upgrade to after 5.1 or later.
See remediation →
99/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 obtain sensitive information, modify data, or cause a denial of service via unknown vectors, aka ZDI-CAN-1661.

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 Automated Network Manager (ANM) before version 5.2 E0401 contain an unspecified vulnerability (ZDI-CAN-1661) that allows remote attackers to obtain sensitive information, modify data, or cause denial of service. The vulnerability has a CVSS score of 9, indicating critical severity and likely network-exploitable without authentication.

MitigationUpgrade HP iMC/ANM to version 5.2 E0401 or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation and restricting access to the management interfaces.

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 For Automated Network ManagerApplication
Affected:<= 5.1
Intelligent Management CenterApplication
Affected:<= 5.1= 5.0= 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
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:C/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. Identify installed HP iMC or ANM version
    On Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\Intelligent Management Center\Version or look at the 'Add/Remove Programs' entry. On Linux, run 'rpm -q imc' or 'dpkg -l | grep imc' if installed via package manager. Alternatively, check the application's About or Help menu if the web interface is accessible.
    Affected if The installed version is 5.0, 5.1, or any version lower than 5.2 E0401.
  2. Confirm product name matches affected software
    Verify the installed product is specifically HP Intelligent Management Center (iMC) or HP Automated Network Manager (ANM). Check the product name in Add/Remove Programs, the web interface login page, or the installation directory structure under C:\hp\imc or /opt/hp/imc.
    Affected if The product is HP iMC or ANM version 5.1 or earlier.
  3. Check if management interface is network-accessible
    Determine if the HP iMC/ANM web console (default ports 8080 or 8443) is exposed to the network. Use 'netstat -an | findstr 8080' on Windows or 'netstat -tuln | grep -E "8080|8443"' on Linux to check if the service is listening on external interfaces.
    Affected if The management interface is reachable from untrusted networks, which combined with a vulnerable version indicates immediate risk.

You are affected if HP Intelligent Management Center or Automated Network Manager is installed at version 5.1 or below (including version 5.0), and the version is earlier than 5.2 E0401.

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 to remediate this vulnerability. If immediate patching is not possible, consider network segmentation and restricting access to the management interfaces.

Recommended fix Moderate confidence

HP Intelligent Management Center 5.2 E0401 or later

  1. 1. Backup current iMC/ANM configuration and database before proceeding with upgrade
  2. 2. Download HP Intelligent Management Center version 5.2 E0401 or later from HP official support site
  3. 3. Stop all iMC/ANM services on the affected server
  4. 4. Run the upgrade installer for version 5.2 E0401
  5. 5. Follow the on-screen upgrade wizard instructions
  6. 6. After upgrade completes, start iMC/ANM services
  7. 7. Verify the application is running correctly and all services are operational
  8. 8. Validate that the previously vulnerable functionality is now patched
Caveat Review HP release notes for 5.2 E0401 for any configuration or compatibility changes before upgrading

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

Fix this in Intelligent Management Center For Automated Network Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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