CVE-2009-0921 in the critical feed json
Multiple heap-based buffer overflows in OvCgi/Toolbar.exe in HP OpenView Network Node Manager (OV NNM) 7.01, 7.51, and 7.53 allow remote at…
published 2009-03-25 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0918
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 13.2%
- EPSS 13.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
Multiple heap-based buffer overflows in OvCgi/Toolbar.exe in HP OpenView Network Node Manager (OV NNM) 7.01, 7.51, and 7.53 allow remote attackers to execute arbitrary code via (1) a long OvAcceptLang cookie, which triggers the error in ov.dll and ovwww.dll, or (2) a long Accept-Language HTTP header, which triggers the error in ovwww.dll or libovwww.so.4.
Exploit prediction
13.24% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- coresecurity.com http://www.coresecurity.com/content/openview-buffer-overflows referenced PoC, tagged "exploit" by a source, unverified
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
-
coresecurity.com
/content/openview-buffer-overflows
exploit
-
marc.info
/?l=bugtraq&m=123791084113871&w=2
vendor-advisory
-
vupen.com
/english/advisories/2009/0819
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49363
vdb-entry
-
securityfocus.com
/bid/34134
vdb-entry
-
securityfocus.com
/archive/1/502054/100/0/threaded
mailing-list
-
securityfocus.com
/bid/34135
vdb-entry
-
secunia.com
/advisories/34444
third-party-advisory
-
securitytracker.com
/id?1021883
vdb-entry
Sources
- CVE List CVE-2009-0921
- NVD CVE-2009-0921
Fencer Vulns 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.