Stack-based buffer overflow in Microsoft HTML Help Workshop 4.74.8702.0, and possibly earlier versions, and as…
No fixed version listed yet.Check the vendor advisory. References ↓
A stack-based buffer overflow in Microsoft HTML Help Workshop 4.74.8702.0 (and possibly earlier versions, including those shipped in the Microsoft HTML Help 1.4 SDK) lies in how the tool processes .hhp project files. An attacker can execute arbitrary code by supplying a crafted .hhp file containing an overly long Contents file field, which requires the victim to open that file in the affected tool.
Official description · CVE.org
Stack-based buffer overflow in Microsoft HTML Help Workshop 4.74.8702.0, and possibly earlier versions, and as included in the Microsoft HTML Help 1.4 SDK, allows context-dependent attackers to execute arbitrary code via a .hhp file with a long Contents file field.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Exploit-DB) was available the same day.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
2 related vulnerabilities in the same code over 3 years.
Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.
- This CVECVE-2006-0564Stack-based buffer overflow in Microsoft HTML Help Workshop…6 Feb 2006
relatedLow
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Stated in the CVE text
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.
- Stated in the CVE text