CVE-2010-1555 in the critical feed json
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…
published 16y ago modified 4mo ago also EUVD-2010-1582
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 62.4%
- EPSS 62.4% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 3
- Metasploit and Exploit-DB
Summary
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 Hostname parameter.
Is CVE-2010-1555 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/windows/http/hp_nnm_getnnmdata_hostname)
- Published
Exploit prediction
62.42% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/http/hp_nnm_getnnmdata_hostname HP OpenView Network Node Manager getnnmdata.exe (Hostname) CGI Buffer Overflow metasploit exploit, great rank, 2010-05-11
- EDB-17047 HP OpenView Network Node Manager (OV NNM) - 'getnnmdata.exe Hostname' CGI Buffer Overflow (Metasploit) remote, 2011-03-25
- EDB-14182 HP OpenView Network Node Manager (OV NNM) - 'getnnmdata.exe' CGI Invalid Hostname Remote Code Execution remote, 2010-07-02
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
marc.info
/?l=bugtraq&m=127360750704351&w=2
vendor-advisory
-
securityfocus.com
/archive/1/511250/100/0/threaded
mailing-list
-
securityfocus.com
/bid/40072
vdb-entry
- zerodayinitiative.com /advisories/ZDI-10-086/
Sources
- CVE List CVE-2010-1555
- NVD CVE-2010-1555
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.