# CVE-2006-3647: Integer overflow in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted Word document that triggers an integer overflow.

- **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:** 10 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jvm5-r77x-76rj

## What is CVE-2006-3647?

CVE-2006-3647 is a critical vulnerability in Microsoft Office, published on 10 Oct 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

Integer overflow in Microsoft Word 2000, 2002, 2003, 2004 for Mac, and v.X for Mac allows remote user-assisted attackers to execute arbitrary code via a crafted string in a Word document, which overflows a 16-bit integer length value, aka "Memmove Code Execution," a different vulnerability than CVE-2006-3651 and CVE-2006-4693.

Weakness: CWE-189

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

It affects 1 product.


Products: Microsoft Office.

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

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

## Is CVE-2006-3647 being exploited?

There is no known exploitation of CVE-2006-3647 in the wild and no public exploit code.

## 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-3647 and fix it if it is affected.

What it is: CVE-2006-3647 is a critical vulnerability in Microsoft Office, published on 10 Oct 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: There is no known exploitation of CVE-2006-3647 in the wild and no public exploit code.

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-3647/ (Markdown: https://insights.sbomify.com/CVE-2006-3647/index.md)
```

## Sources

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

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