Skip to content
Fencer Vulns
critical 10.0

CVE-2009-0133 in the critical feed json

Buffer overflow in Microsoft HTML Help Workshop 4.74 and earlier allows context-dependent attackers to execute arbitrary code via a .hhp fi…

published 2009-01-15 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0142

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
67.0%
EPSS 67.0% chance of exploitation in 30 days, percentile 99.3%
public exploits
8
Metasploit, Exploit-DB

Summary

Buffer overflow in Microsoft HTML Help Workshop 4.74 and earlier allows context-dependent attackers to execute arbitrary code via a .hhp file with a long "Index file" field, possibly a related issue to CVE-2006-0564.

Timeline

  1. First public exploit (EDB-1470)
  2. Published

Exploit prediction

67.05% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/windows/fileformat/hhw_hhp_indexfile_bof HTML Help Workshop 4.74 (hhp Project File) Buffer Overflow metasploit exploit, good rank, 2009-01-17
  • EDB-16631 Microsoft HTML Help Workshop 4.74 - '.hhp' Index Buffer Overflow (Metasploit) (3) local, 2010-09-25
  • EDB-10321 Microsoft HTML Help Workshop 4.74 - '.hhp' Local Buffer Overflow (1) local, 2009-12-05
  • EDB-7727 Microsoft HTML Workshop 4.74 - Universal Buffer Overflow local, 2009-01-12
  • EDB-1495 Microsoft HTML Help Workshop - '.hhp' Local Buffer Overflow (3) local, 2006-02-14
  • EDB-1490 Microsoft HTML Help Workshop - '.hhp' Local Buffer Overflow (2) local, 2006-02-11
  • EDB-1488 Microsoft HTML Help Workshop - '.hhp' Denial of Service dos, 2006-02-10
  • EDB-1470 Microsoft HTML Help Workshop - '.hhp' Local Buffer Overflow (1) local, 2006-02-06

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

Sources

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.