# CVE-2006-2111: Information disclosure in n/a

> Remote attackers can bypass domain restrictions to obtain sensitive information via mhtml URI redirections in Outlook Express.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 1 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7pg3-hjwr-p72r

## What is CVE-2006-2111?

CVE-2006-2111 is a medium-severity vulnerability in n/a, published on 1 May 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

A component in Microsoft Outlook Express 6 allows remote attackers to bypass domain restrictions and obtain sensitive information via redirections with the mhtml: URI handler, as originally reported for Internet Explorer 6 and 7, aka "URL Redirect Cross Domain Information Disclosure Vulnerability."

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Microsoft Outlook Express.

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

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

## Is CVE-2006-2111 being exploited?

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

Public exploit code:

- Outlook Express 5.5/6.0 / Windows Mail - MHTML URI Handler Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-0380](https://insights.sbomify.com/CVE-2004-0380/): Security feature bypass in n/a (critical 10.0)
- [CVE-2010-3147](https://insights.sbomify.com/CVE-2010-3147/): Path traversal in n/a (critical 9.3)
- [CVE-2010-0816](https://insights.sbomify.com/CVE-2010-0816/): Integer overflow in n/a (critical 9.3)
- [CVE-2007-3897](https://insights.sbomify.com/CVE-2007-3897/): Memory corruption in n/a (critical 9.3)
- [CVE-2001-1547](https://insights.sbomify.com/CVE-2001-1547/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2111 is a medium-severity vulnerability in n/a, published on 1 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2111 exists.

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

## Sources

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

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