CVE-2011-0266 in the critical feed json
Buffer overflow in nnmRptConfig.exe in HP OpenView Network Node Manager (OV NNM) 7.51 and 7.53 allows remote attackers to execute arbitrary…
published 2011-01-13 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0292
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 70.1%
- EPSS 70.1% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Buffer overflow in nnmRptConfig.exe in HP OpenView Network Node Manager (OV NNM) 7.51 and 7.53 allows remote attackers to execute arbitrary code via a long nameParams parameter, a different vulnerability than CVE-2011-0267.2.
Timeline
- First public exploit (Metasploit exploit/windows/http/hp_nnm_nnmrptconfig_nameparams)
- Published
Exploit prediction
70.11% 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_nnmrptconfig_nameparams HP OpenView NNM nnmRptConfig nameParams Buffer Overflow metasploit exploit, normal rank, 2011-01-10
- EDB-17028 HP OpenView Network Node Manager (OV NNM) - nnmRptConfig nameParams 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
-
securityfocus.com
/archive/1/515628
vendor-advisory
-
vupen.com
/english/advisories/2011/0085
vdb-entry
- zerodayinitiative.com /advisories/ZDI-11-008/
-
securityreason.com
/securityalert/8151
third-party-advisory
-
securityfocus.com
/bid/45762
vdb-entry
-
securitytracker.com
/id?1024951
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64650
vdb-entry
Sources
- CVE List CVE-2011-0266
- NVD CVE-2011-0266
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.