# CVE-2005-0420: Open redirect in n/a

> Remote attackers can redirect Exchange OWA users to arbitrary malicious URLs via crafted links, requiring user interaction to exploit.

- **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:** 15 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ghcm-xhwj-hh9q

## What is CVE-2005-0420?

CVE-2005-0420 is a medium-severity vulnerability in Microsoft Exchange Server, published on 15 Feb 2005. 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 Web Access (OWA), when used with Exchange, allows remote attackers to redirect users to arbitrary URLs for login via a link to the owalogon.asp application.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2005-0420?

It affects 1 product.


Products: Microsoft Exchange Server.

## How do I fix CVE-2005-0420?

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

## Is CVE-2005-0420 being exploited?

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

Public exploit code:

- Microsoft Outlook 2003 - Web Access Login Form Remote URI redirection (exploitdb)

## Other vulnerabilities in Microsoft Exchange Server

- [CVE-2024-21410](https://insights.sbomify.com/CVE-2024-21410/): Microsoft Exchange Server Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2021-34473](https://insights.sbomify.com/CVE-2021-34473/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-26855](https://insights.sbomify.com/CVE-2021-26855/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-34523](https://insights.sbomify.com/CVE-2021-34523/): Microsoft Exchange Server Privilege Escalation (critical 9.0, exploited in the wild)
- [CVE-2023-21529](https://insights.sbomify.com/CVE-2023-21529/): Microsoft Exchange Server Deserialization of Untrusted Data (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0420 and fix it if it is affected.

What it is: CVE-2005-0420 is a medium-severity vulnerability in Microsoft Exchange Server, published on 15 Feb 2005. 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-2005-0420 exists.

Affected product: Microsoft Exchange Server. 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-2005-0420/ (Markdown: https://insights.sbomify.com/CVE-2005-0420/index.md)
```

## Sources

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

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