CVE-2010-1552 in the critical feed json
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 allo…
published 16y ago modified 4mo ago also EUVD-2010-1579
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 67.1%
- EPSS 67.1% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
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.
Is CVE-2010-1552 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_snmpviewer_actapp)
- Published
Exploit prediction
67.09% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/http/hp_nnm_snmpviewer_actapp HP OpenView Network Node Manager snmpviewer.exe Buffer Overflow metasploit exploit, great rank, 2010-05-11
- EDB-17039 HP OpenView Network Node Manager (OV NNM) - 'snmpviewer.exe' Remote Buffer Overflow (Metasploit) remote, 2011-03-23
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
-
securityreason.com
/securityalert/8157
third-party-advisory
-
securityfocus.com
/archive/1/511248/100/0/threaded
mailing-list
- zerodayinitiative.com /advisories/ZDI-10-083/
Sources
- CVE List CVE-2010-1552
- NVD CVE-2010-1552
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.