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

> Attackers can execute arbitrary JavaScript and redirect users via malicious Excel files containing embedded Flash objects, requiring user interaction to open the file.

- **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:** 22 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4v5q-p386-f6mv

## What is CVE-2006-3014?

CVE-2006-3014 is a medium-severity code injection vulnerability in Microsoft Excel, published on 22 Jun 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

Microsoft Excel allows user-assisted attackers to execute arbitrary javascript and redirect users to arbitrary sites via an Excel spreadsheet with an embedded Shockwave Flash Player ActiveX Object, which is automatically executed when the user opens the spreadsheet.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Microsoft Excel.

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

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

## Is CVE-2006-3014 being exploited?

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

Public exploit code:

- Microsoft Office 2003 - Embedded Shockwave Flash Object Security Bypass (exploitdb)

## Other vulnerabilities in Microsoft Excel

- [CVE-2019-1297](https://insights.sbomify.com/CVE-2019-1297/): Microsoft Excel Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2009-0238](https://insights.sbomify.com/CVE-2009-0238/): Microsoft Office Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2016-7262](https://insights.sbomify.com/CVE-2016-7262/): Microsoft Office Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2009-3129](https://insights.sbomify.com/CVE-2009-3129/): Microsoft Excel Featheader Record Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2008-0081](https://insights.sbomify.com/CVE-2008-0081/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3014 is a medium-severity code injection vulnerability in Microsoft Excel, published on 22 Jun 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-3014 exists.

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

## Sources

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

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