# CVE-2006-2055: Command injection in n/a

> Attackers can inject command line arguments via mailto links in Outlook, potentially executing arbitrary code with user interaction.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 26 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-grxh-vgg4-3pff

## What is CVE-2006-2055?

CVE-2006-2055 is a medium-severity command injection vulnerability in Microsoft Outlook, published on 26 Apr 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

Argument injection vulnerability in Microsoft Outlook 2003 SP1 allows user-assisted remote attackers to modify command line arguments to an invoked mail client via " (double quote) characters in a mailto: scheme handler, as demonstrated by launching Microsoft Outlook with an arbitrary filename as an attachment.  NOTE: it is not clear whether this issue is implementation-specific or a problem in the Microsoft API.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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

It affects 1 product.


Products: Microsoft Outlook.

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

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

## Is CVE-2006-2055 being exploited?

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

## Other vulnerabilities in Microsoft Outlook

- [CVE-2017-11774](https://insights.sbomify.com/CVE-2017-11774/): Microsoft Office Outlook Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2001-0538](https://insights.sbomify.com/CVE-2001-0538/): Code injection in n/a (critical 10.0)
- [CVE-2013-3870](https://insights.sbomify.com/CVE-2013-3870/): Use after free in n/a (critical 9.3)
- [CVE-2010-2728](https://insights.sbomify.com/CVE-2010-2728/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0266](https://insights.sbomify.com/CVE-2010-0266/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2055 is a medium-severity command injection vulnerability in Microsoft Outlook, published on 26 Apr 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-2055 in the wild and no public exploit code.

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

## Sources

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

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