CVE-2010-1553
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 · uneditedStack-based buffer overflow in getnnmdata.exe in HP OpenView Network Node Manager (OV NNM) 7.01, 7.51, and 7.53 allows remote attackers to execute arbitrary code via an invalid MaxAge 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 confidenceStack-based buffer overflow in getnnmdata.exe of HP OpenView Network Node Manager versions 7.01, 7.51, and 7.53 allows remote attackers to execute arbitrary code via an invalid MaxAge parameter, achieving maximum CVSS score of 10 due to trivial network exploitability and complete system 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.0.1= 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 installedCheck for NNM installation directory (typically C:\Program Files\HP\OpenView or /opt/OV) and look for ovNNM executable or HP OpenView related binariesAffected if HP OpenView NNM software is present on the system
-
Identify installed NNM versionRun 'ovstatus' command or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\HP\OpenView\NodeManager\Version, or examine the getnnmdata.exe file properties for version informationAffected if Version is 7.01, 7.51, or 7.53 (or displays as 7.0.1, 7.51, 7.53)
-
Verify getnnmdata.exe component existsSearch for getnnmdata.exe in the NNM installation tree (commonly in bin or cgi-bin directories)Affected if getnnmdata.exe file is present on the system
-
Check network exposure of NNM web servicesReview firewall rules and network access lists for ports 80, 443, or 3443 (typical NNM HTTP/HTTPS ports) to determine if getnnmdata.exe CGI component is accessible from untrusted networksAffected if NNM web interface ports are accessible from outside the trusted network
-
Inspect running NNM servicesUse netstat or similar tool to identify if ovwdb, ovwebem, or related NNM services are listening on network interfaces, particularly the web server component that exposes getnnmdata.exeAffected if NNM web services are running and listening on network interfaces
System is affected if HP OpenView NNM versions 7.01, 7.51, or 7.53 are installed with the getnnmdata.exe component accessible on the network.
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 vendor-supplied HP security patches for CVE-2010-1553; if patches unavailable, disable the affected getnnmdata.exe component and implement network segmentation to restrict access to NNM services.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1553 — 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-2010-1553 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