Openview Network Node ManagerApplication · Hp

CVE-2010-1551

HIGH · 10.0 CVSS v2.0 Published 2010-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Stack-based buffer overflow in the _OVParseLLA function in ov.dll in netmon.exe in Network Monitor in HP OpenView Network Node Manager (OV NNM) 7.01, 7.51, and 7.53 allows remote attackers to execute arbitrary code via the sel parameter.

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 · high confidence

Stack-based buffer overflow in the _OVParseLLA function in ov.dll within netmon.exe in HP OpenView Network Node Manager versions 7.01, 7.51, and 7.53 allows remote attackers to execute arbitrary code via a crafted 'sel' parameter.

MitigationApply HP vendor patches for this vulnerability or upgrade to a patched version of OpenView Network Node Manager; until patched, restrict network access to the netmon.exe service and implement network segmentation to reduce exposure.

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
Openview Network Node ManagerApplication
Affected:= 7.0.1= 7.51= 7.53

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if HP OpenView Network Node Manager is installed
    Check for the presence of the OpenView Network Node Manager installation directory, typically found under C:\Program Files\HP\OpenView or similar locations. Use system inventory or installed software listings to confirm the product is present.
    Affected if HP OpenView Network Node Manager is installed on the system.
  2. Determine the installed version
    Locate the version information for the installed HP OpenView Network Node Manager. This is typically available in the product's about dialog, registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\HP\OpenView, or version information on the netmon.exe binary itself.
    Affected if The installed version is 7.01, 7.51, or 7.53.
  3. Verify netmon.exe is present
    Locate the netmon.exe executable in the OpenView installation directory, typically in the bin or similar subfolder. Use file system search or inspect the installation folder directly.
    Affected if The netmon.exe file exists in the OpenView installation directory.
  4. Check if netmon.exe service is running
    Open Windows Services console (services.msc) or run 'sc query' command to check the status of the Network Node Manager service. Also verify if port 2711 (default netmon port) is listening using netstat or similar tool.
    Affected if The netmon.exe process or Network Node Manager service is currently running and listening on a network port.
  5. Confirm ov.dll library version
    Locate ov.dll in the OpenView installation directory, right-click the file, select Properties, and examine the Version tab to identify the file version.
    Affected if The ov.dll file version corresponds to the vulnerable versions (7.01, 7.51, or 7.53) of the product.

The system is affected if HP OpenView Network Node Manager versions 7.01, 7.51, or 7.53 are installed AND the netmon.exe service is running.

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 HP vendor patches for this vulnerability or upgrade to a patched version of OpenView Network Node Manager; until patched, restrict network access to the netmon.exe service and implement network segmentation to reduce exposure.

Fix this in Openview Network Node Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-1551 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-1551 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