dbcve.org
Network Node Manager IApplication · Hp

CVE-2012-3267

MEDIUM · 5.0 CVSS v2.0 Published 2012-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 Network Node Manager i (NNMi) 9.20 allows remote attackers to obtain sensitive information 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 confidence

HP Network Node Manager i (NNMi) version 9.20 contains an unspecified vulnerability that allows remote attackers to obtain sensitive information via unknown vectors. The CVSS score of 5 indicates a moderate-severity information disclosure issue with network-level accessibility.

MitigationApply the HP patch for CVE-2012-3267 if available, or upgrade to a newer supported version of NNMi. Restrict network access to NNMi management interfaces to authorized personnel only until a fix is deployed.

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
Network Node Manager IApplication
Affected:= 9.20

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
None
Availability
None

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

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 NNMi is installed
    Check for HP Network Node Manager i installation directories (e.g., C:\Program Files\HP\NNM or /opt/HP/NNM) or look for NNMi processes running on the system
    Affected if HP NNMi software is present on the system
  2. Confirm the installed version is 9.20
    Access the NNMi web console About page (typically http://hostname:8080/nnm/about) or run 'ovoo -version' from the NNMi bin directory, or check version in the installation properties file
    Affected if The version listed is exactly 9.20
  3. Determine if NNMi management interface is network-accessible
    Check firewall rules and network configuration to see if ports 80, 443, or 8080 (NNMi web interface ports) are open to untrusted networks
    Affected if The NNMi web console is accessible from network addresses other than localhost or trusted management subnets

You are affected if HP NNMi version 9.20 is installed AND its management interface is accessible over the network, as the information disclosure flaw can be exploited remotely.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the HP patch for CVE-2012-3267 if available, or upgrade to a newer supported version of NNMi. Restrict network access to NNMi management interfaces to authorized personnel only until a fix is deployed.

Fix this in Network Node Manager I Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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