CVE-2011-3167
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 OpenView Network Node Manager (OV NNM) 7.51 and 7.53 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1210.
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 OpenView Network Node Manager (OV NNM) versions 7.51 and 7.53 contain an unspecified vulnerability (ZDI-CAN-1210) that allows remote attackers to execute arbitrary code via unknown vectors. The CVSS score of 10 indicates critical severity with complete compromise potential.
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= 7.51= 7.53CVSS 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.
-
Confirm HP OpenView Network Node Manager is installedLocate the OVN NNM installation directory and verify the executable files are present on the system. Common locations include /opt/OV or C:\Program Files\HP OpenView on Windows.Affected if The software is present on the system and no version check can be performed, assume affected if version cannot be determined.
-
Identify the installed version of OVN NNMRun the version check command for your OVN NNM installation. This is typically done via the 'ovoo' command-line utility, or by checking the version properties of the main executable (ovnnm.exe on Windows, or the bin/ovnnm binary on Unix/Linux).Affected if The installed version equals exactly 7.51 or exactly 7.53.
-
Check if the OVN NNM web interface is accessibleVerify if the embedded web server (ovwdb or webapp) is listening on network ports (default ports include 80, 443, or 3443). Use 'netstat' or similar tools to list open ports and confirm the service is network-accessible.Affected if The OVN NNM web interface is exposed to the network, making the vulnerability exploitable remotely.
-
Verify the OpenView process is runningCheck if the ovw or ovnnm processes are currently running on the system using process monitoring tools (ps on Unix/Linux, Task Manager or tasklist on Windows).Affected if The vulnerable software is actively running and exploitable.
The environment is affected if HP OpenView Network Node Manager version 7.51 or 7.53 is installed and running, particularly if the web interface is network-accessible.
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 dataIsolate affected OVN NNM systems from untrusted networks immediately. Apply HP security patches if available, or implement compensating controls such as network segmentation and strict access controls to reduce exposure until remediation is possible.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3167 — 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-2011-3167 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