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

> Remote attackers can bypass access restrictions in Outlook Express to load arbitrary content, facilitating phishing attacks via BASE HREF manipulation.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 6 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-w6p4-h264-pgp8

## What is CVE-2004-2694?

CVE-2004-2694 is a medium-severity vulnerability in n/a, published on 6 Oct 2007. 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

Microsoft Outlook Express 6.0 allows remote attackers to bypass intended access restrictions, load content from arbitrary sources into the Outlook context, and facilitate phishing attacks via a "BASE HREF" with the target set to "_top".

Weakness: CWE-264

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

It affects 1 product.


Products: Microsoft Outlook Express.

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

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

## Is CVE-2004-2694 being exploited?

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

## 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-2004-2694 and fix it if it is affected.

What it is: CVE-2004-2694 is a medium-severity vulnerability in n/a, published on 6 Oct 2007. 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-2004-2694 in the wild and no public exploit code.

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

## Sources

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

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