CVE-2011-3165
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-1208.
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 versions 7.51 and 7.53 contain an unspecified vulnerability allowing remote unauthenticated attackers to execute arbitrary code. This is a critical network-based RCE vulnerability in enterprise network management software, likely exploitable without authentication.
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.
-
Verify HP OpenView Network Node Manager is installedCheck for NNM installation directories (typically C:\HP\OpenView or /opt/OV) or look for the 'ovbbccb' and 'NNM' processes running on the systemAffected if The software is present on the system
-
Determine the installed NNM versionCheck the version file in the installation directory, or run 'ovoo -version' or 'ovstatus' command if available, or inspect registry key HKEY_LOCAL_MACHINE\SOFTWARE\HP\OpenView\Version on WindowsAffected if The version is 7.51 or 7.53 exactly (not ranges, only these two versions are affected)
-
Identify if NNMTopO web service is enabledCheck if the web-based management interface (typically on port 80 or 443) or the NNMTopO service (ovtopmd) is running and accessibleAffected if The web management interface or NNMTopO service is exposed and running
-
Check network exposure of NNM servicesIdentify all listening ports associated with NNM (common ports: 80, 443, 7510, 7511, 7512) using netstat or similar tool, and determine if they are bound to non-loopback interfaces accessible from networkAffected if NNM services are listening on interfaces reachable from untrusted networks
-
Confirm remote access is unauthenticatedVerify whether the web management interface or API endpoints allow access without authentication credentials or session tokensAffected if The NNM management interface permits unauthenticated access
You are affected if HP OpenView Network Node Manager version 7.51 or 7.53 is installed and its management services are network-accessible without requiring authentication.
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 OV NNM or upgrade to a fixed version beyond 7.53. Network segmentation and firewall rules can limit exposure to trusted networks only.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3165 — 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-3165 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