CVE-2012-3275
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 Network Node Manager i (NNMi) 9.1x and 9.20 allows remote attackers to execute arbitrary code via unknown vectors.
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 Network Node Manager i (NNMi) versions 9.1x and 9.20 contain an unspecified vulnerability allowing remote attackers to execute arbitrary code via unknown vectors. The CVSS score of 10 indicates a critical, easily exploitable flaw requiring no authentication and providing complete system 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= 9.10= 9.20CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if HP NNMi is installedLocate HP Network Node Manager i installation directory, typically under /opt/HP/NNM or C:\Program Files\HP\NNM on Linux or Windows systems respectively. Check for nnm binaries or services.Affected if HP NNMi software is found installed on the system
-
Determine installed NNMi versionRun command to retrieve NNMi version, such as 'nnmversion -version' or inspect version file in installation directory if available. Compare result to affected versions 9.10 through 9.20.Affected if Installed version matches 9.10, 9.11, 9.12, 9.13, 9.14, 9.15, 9.16, 9.17, 9.18, 9.19, or 9.20
-
Verify NNMi management services are runningCheck if NNMi httpd, webapp, or related processes are active. On Linux use 'ps -ef | grep -i nnm' or on Windows check Windows Services for 'HP Network Node Manager i' service status.Affected if NNMi management services are running and accessible
-
Assess network exposure of NNMi interfacesReview firewall rules and network configuration to determine if NNMi management ports (typically 80, 443, or 8080) are exposed to untrusted networks or the internet.Affected if NNMi management interfaces are reachable from untrusted network segments
System is affected if HP NNMi version 9.10 through 9.20 is installed with management services running and potentially exposed to network access.
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 dataApply HP security patches for this vulnerability or upgrade to a patched version of NNMi. If patches are unavailable, restrict network access to NNMi management interfaces and monitor for indicators of compromise.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2012-3275 — 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-3275 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