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

> Attackers can execute arbitrary code by tricking users into opening a malicious Excel file with a crafted DATETIME record.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 10 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8fr2-m6qv-rmxc

## What is CVE-2006-2387?

CVE-2006-2387 is a medium-severity memory corruption vulnerability in Microsoft Office, published on 10 Oct 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 Excel 2000, 2002, 2003, 2004 for Mac, v.X for Mac, Excel Viewer 2003, and Microsoft Works Suite 2004 through 2006 allows user-assisted attackers to execute arbitrary code via a crafted DATETIME record in an XLS file, a different vulnerability than CVE-2006-3867 and CVE-2006-3875.

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

It affects 1 product.


Products: Microsoft Office.

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

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

## Is CVE-2006-2387 being exploited?

There is no known exploitation of CVE-2006-2387 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-2387 and fix it if it is affected.

What it is: CVE-2006-2387 is a medium-severity memory corruption vulnerability in Microsoft Office, published on 10 Oct 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: There is no known exploitation of CVE-2006-2387 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-2387/ (Markdown: https://insights.sbomify.com/CVE-2006-2387/index.md)
```

## Sources

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

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