# CVE-2006-3877: Code injection in n/a

> User-assisted attackers can execute arbitrary code via a crafted PowerPoint file in Microsoft Office.

- **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:** 10 Oct 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j86v-2r4w-rjjr

## What is CVE-2006-3877?

CVE-2006-3877 is a critical code injection vulnerability in Microsoft Excel, 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 PowerPoint in Microsoft Office 2000, Office 2002, Office 2003, Office 2004 for Mac, and Office v.X for Mac allows user-assisted attackers to execute arbitrary code via an unspecified "crafted file," a different vulnerability than CVE-2006-3435, CVE-2006-4694, and CVE-2006-3876.

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

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

It affects 14 products.


Products: Microsoft Access, Microsoft Excel, Microsoft Excel Viewer, Microsoft Frontpage, Microsoft Infopath, Microsoft Office, Microsoft Onenote, Microsoft Outlook, Microsoft Powerpoint, Microsoft Project, Microsoft Publisher, Microsoft Visio, Microsoft Word, Microsoft Word Viewer.

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

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

## Is CVE-2006-3877 being exploited?

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

## Other vulnerabilities in Microsoft Excel

- [CVE-2007-0671](https://insights.sbomify.com/CVE-2007-0671/): Microsoft Office Excel Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2000-0788](https://insights.sbomify.com/CVE-2000-0788/): Code injection in n/a (critical 10.0)
- [CVE-2015-2503](https://insights.sbomify.com/CVE-2015-2503/): Security feature bypass in n/a (critical 9.3)
- [CVE-2013-3155](https://insights.sbomify.com/CVE-2013-3155/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3156](https://insights.sbomify.com/CVE-2013-3156/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3877 is a critical code injection vulnerability in Microsoft Excel, 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-3877 in the wild and no public exploit code.

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

## Sources

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

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