Openview Network Node ManagerApplication · Hp

CVE-2010-1552

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
High EPSS 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 doLoad function in snmpviewer.exe in HP OpenView Network Node Manager (OV NNM) 7.01, 7.51, and 7.53 allows remote attackers to execute arbitrary code via the act and app parameters.

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 vulnerability in the doLoad function of snmpviewer.exe in HP OpenView Network Node Manager versions 7.01, 7.51, and 7.53. The vulnerability is triggered via the act and app parameters, allowing remote attackers to inject and execute arbitrary code due to insufficient bounds checking on user-supplied input before copying to a stack buffer.

MitigationApply the HP security patch for this vulnerability; if unavailable, restrict network access to the snmpviewer.exe component and consider upgrading to a supported version of HP OpenView Network Node Manager.

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. Confirm HP OpenView Network Node Manager is installed
    Check for the presence of the HP OpenView Network Node Manager installation directory, typically found under C:\Program Files\HP\OpenView or C:\HP\OpenView on Windows systems. Look for the snmpviewer.exe binary in the web publishing directory (usually under the webapp or www directory).
    Affected if The product is installed and snmpviewer.exe exists in the installation tree.
  2. Identify the installed version of HP OpenView Network Node Manager
    Locate the version information file or check the product version through the Windows Add/Remove Programs utility, or examine version metadata in the snmpviewer.exe file properties if available. Compare the installed version to the affected range: 7.01, 7.51, or 7.53.
    Affected if The installed version is exactly 7.01, 7.51, or 7.53.
  3. Determine if the snmpviewer.exe web interface is accessible
    Check the network configuration to see if the OVN NMS web server (port typically 80 or 443) is listening and accessible. Verify that the snmpviewer.exe CGI or ISAPI component is exposed through the web server configuration.
    Affected if The snmpviewer.exe component is accessible over the network via HTTP/HTTPS.
  4. Verify the vulnerable doLoad function is present in snmpviewer.exe
    If possible, examine the snmpviewer.exe binary for the presence of the doLoad function, or confirm through HP documentation that the vulnerable CGI script is part of the installed build.
    Affected if The doLoad function exists in the installed snmpviewer.exe binary.

A user is affected if HP OpenView Network Node Manager versions 7.01, 7.51, or 7.53 are installed AND the snmpviewer.exe web component is accessible over the network.

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 security patch for this vulnerability; if unavailable, restrict network access to the snmpviewer.exe component and consider upgrading to a supported version of HP OpenView Network Node Manager.

Fix this in Openview Network Node Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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