# CVE-2006-0564: Memory corruption in n/a

> A stack-based buffer overflow in Microsoft HTML Help Workshop allows attackers to execute arbitrary code by tricking users into opening a malicious .hhp file.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-937c-j3f9-3p46

## What is CVE-2006-0564?

CVE-2006-0564 is a high-severity memory corruption vulnerability in n/a, published on 6 Feb 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

## Which versions are affected by CVE-2006-0564?

It affects 2 products.


Products: Microsoft Html Help, Microsoft Html Help Workshop.

## How do I fix CVE-2006-0564?

No fix has been published for CVE-2006-0564 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-0564 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0564 exists.

Public exploit code:

- Microsoft HTML Help Workshop - '.hhp' Local Buffer Overflow (1) (exploitdb)
- HTML Help Workshop 4.74 (hhp Project File) Buffer Overflow (metasploit)
- HTML Help Workshop 4.74 (hhp Project File) Buffer Overflow (metasploit)
- Microsoft HTML Help Workshop - '.hhp' Denial of Service (exploitdb)
- Microsoft HTML Help Workshop - '.hhp' Local Buffer Overflow (2) (exploitdb)
- Microsoft HTML Help Workshop - '.hhp' Local Buffer Overflow (3) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0564 and fix it if it is affected.

What it is: CVE-2006-0564 is a high-severity memory corruption vulnerability in n/a, published on 6 Feb 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-0564 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-0564/ (Markdown: https://insights.sbomify.com/CVE-2006-0564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-0564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-0564
- OSV: https://osv.dev/vulnerability/CVE-2006-0564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-0564/
Summaries are generated and may contain mistakes; the official description above is the record.