# CVE-2004-0380: Security feature bypass in n/a

> Remote attackers can bypass domain restrictions and execute arbitrary code via MHTML protocol handlers in Outlook Express, requiring user interaction.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 6 Apr 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wv58-cxvm-2w2g

## What is CVE-2004-0380?

CVE-2004-0380 is a critical vulnerability in n/a, published on 6 Apr 2004. 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

The MHTML protocol handler in Microsoft Outlook Express 5.5 SP2 through Outlook Express 6 SP1 allows remote attackers to bypass domain restrictions and execute arbitrary code, as demonstrated on Internet Explorer using script in a compiled help (CHM) file that references the InfoTech Storage (ITS) protocol handlers such as (1) ms-its, (2) ms-itss, (3) its, or (4) mk:@MSITStore, aka the "MHTML URL Processing Vulnerability."

## Which versions are affected by CVE-2004-0380?

It affects 1 product.


Products: Microsoft Outlook Express.

## How do I fix CVE-2004-0380?

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

## Is CVE-2004-0380 being exploited?

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

Public exploit code:

- Microsoft Outlook Express 6.0 - '.MHTML' Forced File Execution (1) (exploitdb)
- Microsoft Outlook Express 6.0 - MHTML Forced File Execution (2) (exploitdb)
- Microsoft Internet Explorer 5.0.1 - ITS Protocol Zone Bypass (MS04-013) (exploitdb)

## Other vulnerabilities in n/a

- [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)
- [CVE-2005-1213](https://insights.sbomify.com/CVE-2005-1213/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0380 and fix it if it is affected.

What it is: CVE-2004-0380 is a critical vulnerability in n/a, published on 6 Apr 2004. 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-2004-0380 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-2004-0380/ (Markdown: https://insights.sbomify.com/CVE-2004-0380/index.md)
```

## Sources

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

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