CVE-2012-5204
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 · uneditedUnspecified 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-1614.
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 confidenceHP Intelligent Management Center (iMC) and ANM versions before 5.2 E0401 contain an unspecified vulnerability (ZDI-CAN-1614) that allows remote attackers to obtain sensitive information, modify data, or cause denial of service via unknown vectors. The vulnerability is exploitable remotely without authentication and affects enterprise network management infrastructure.
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<= 5.1= 5.0= 5.1<= 5.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if HP iMC or ANM is installedCheck installed programs on Windows systems for 'HP Intelligent Management Center' or 'HP IMC' or 'ANM' or 'Automated Network Manager' in the program list, or check services.msc for HP iMC servicesAffected if Either product is found on the system
-
Determine the installed version of HP iMCLocate the iMC installation directory (commonly C:\Program Files\HP\iMC\ or similar) and check for a version file, or right-click the iMC application executable and view Properties > Details for version informationAffected if Version is 5.1 or lower, or version cannot be determined and product is present
-
Determine the installed version of ANMLocate the ANM installation directory and check for version information in application files or check Windows services for ANM version detailsAffected if Version is 5.1 or lower, or version cannot be determined and product is present
-
Check if management ports are exposedUse netstat -an to check if common HP iMC ports (typically 8080, 8443, or custom ports configured during installation) are listening on external network interfaces (0.0.0.0 rather than 127.0.0.1)Affected if Management ports are listening on non-localhost interfaces
-
Verify if the service is runningOpen services.msc and check if HP iMC Core Service, HP iMC DBService, or ANM services are currently runningAffected if Affected versions are running
The environment is affected if HP Intelligent Management Center or ANM versions 5.1 or below are installed and running, especially if management interfaces are accessible from the network.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade HP iMC/ANM to version 5.2 E0401 or later to address this vulnerability. If immediate patching is not possible, restrict network access to management interfaces and monitor for signs of exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5204 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-5204 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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