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

> User-assisted attackers can execute arbitrary code via a malformed Office file triggering memory corruption, affecting Microsoft Office users.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mc3v-59x4-8r59

## What is CVE-2006-2389?

CVE-2006-2389 is a critical memory corruption vulnerability in Microsoft Office, published on 11 Jul 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

Unspecified vulnerability in Microsoft Office 2003 SP1 and SP2, Office XP SP3, Office 2000 SP3, and other products, allows user-assisted attackers to execute arbitrary code via an Office file with a malformed property that triggers memory corruption related to record lengths, aka "Microsoft Office Property Vulnerability," a different vulnerability than CVE-2006-1316.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Microsoft Office.

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

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

## Is CVE-2006-2389 being exploited?

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

Public exploit code:

- Microsoft Office 2000/2002 - Property Code Execution (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-2389 and fix it if it is affected.

What it is: CVE-2006-2389 is a critical memory corruption vulnerability in Microsoft Office, published on 11 Jul 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-2389 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-2389/ (Markdown: https://insights.sbomify.com/CVE-2006-2389/index.md)
```

## Sources

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

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