Vulnerability record · CVE-2010-1553 · published 13 May 2010
CVE-2010-1553: HP OpenView Network Node Manager getnnmdata.exe stack buffer overflow
Hp · Openview Network Node Manager
getnnmdata.exe in HP OpenView Network Node Manager 7.01, 7.51 and 7.53 contains a stack-based buffer overflow triggered by an invalid MaxAge parameter. Because the flaw is remotely reachable without authentication and yields full code execution, it is a serious pre-auth risk to exposed NNM deployments.
Description
Stack-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.
AV:N/AC:L/Au:N/C:C/I:C/A:C
Automated analysis
critical priorityUnauthenticated remote code execution with a CVSS 2.0 score of 10 and very high EPSS probability makes this an urgent exposure for any internet- or broadly reachable NNM instance.
What it is
getnnmdata.exe in HP OpenView Network Node Manager 7.01, 7.51 and 7.53 contains a stack-based buffer overflow triggered by an invalid MaxAge parameter. Because the flaw is remotely reachable without authentication and yields full code execution, it is a serious pre-auth risk to exposed NNM deployments.
Impact
A remote attacker can execute arbitrary code with the privileges of the getnnmdata.exe process, giving full compromise of confidentiality, integrity and availability on the host. The CVSS 2.0 vector rates this complete impact across all three categories.
Attack surface
Reached over the network via the getnnmdata.exe component with a crafted MaxAge parameter; the AV:N/AC:L/Au:N vector indicates no authentication and no user interaction are required. Any NNM instance exposing this interface to untrusted networks is directly reachable.
Exploitation
CISA KEV does not list this CVE, but EPSS is very high at roughly 0.71 (99th percentile), suggesting elevated likelihood of exploitation activity. The references are vendor and researcher advisories with no exploit tags, so public exploit code is not confirmed by this record.
What to do
- Apply the HP patch for the affected NNM versions (7.01, 7.51, 7.53) or upgrade to a supported release.
- Restrict network access to the getnnmdata.exe interface with firewall rules or ACLs so only trusted management hosts can reach it.
- If patching is not immediately possible, disable or block the vulnerable component and monitor for attempts against it.
- Segment NNM management infrastructure from general user and internet-facing networks.
- Validate and bound-check the MaxAge parameter at any proxy or filtering layer in front of NNM.
Detection
- Monitor network traffic and logs for requests to getnnmdata.exe containing unusually long or malformed MaxAge values.
- Alert on getnnmdata.exe process crashes or abnormal termination on NNM hosts.
- Watch for unexpected child processes or command execution spawned by getnnmdata.exe.
- Review NNM host logs for anomalous inbound connections from untrusted source addresses.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2010-1553 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2010-1553), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.