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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious DOC file in Microsoft Word.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q2rf-7vjv-wx6h

## What is CVE-2006-6561?

CVE-2006-6561 is a critical memory corruption vulnerability in Microsoft Office, published on 14 Dec 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in Microsoft Word 2000, 2002, and Word Viewer 2003 allows user-assisted remote attackers to execute arbitrary code via a crafted DOC file that triggers memory corruption, as demonstrated via the 12122006-djtest.doc file, a different issue than CVE-2006-5994 and CVE-2006-6456.

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

It affects 4 products.


Products: Microsoft Office, Microsoft Word, Microsoft Word Viewer, Microsoft Works.

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

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

## Is CVE-2006-6561 being exploited?

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

Public exploit code:

- Microsoft Word Document - Malformed Pointer (PoC) (exploitdb)

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6561 is a critical memory corruption vulnerability in Microsoft Office, published on 14 Dec 2006. An attacker can exploit it over the internet without logging in, 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-6561 exists.

Affected product: Microsoft Office. 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-6561/ (Markdown: https://insights.sbomify.com/CVE-2006-6561/index.md)
```

## Sources

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

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