# CVE-2017-8621: Open redirect in Microsoft Exchange Server 2010 SP3, Exchange Server 2013 SP3, Exchange Server 2013 CU16, and Exchange Server 2016 CU5.

> Attackers can exploit an open redirect in Microsoft Exchange Server to spoof trusted sites and potentially trick users into visiting malicious URLs.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 11 Jul 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vfc8-gvw2-fjv6

## What is CVE-2017-8621?

CVE-2017-8621 is a medium-severity vulnerability in Microsoft Exchange Server, published on 11 Jul 2017. 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 Exchange Server 2010 SP3, Exchange Server 2013 SP3, Exchange Server 2013 CU16, and Exchange Server 2016 CU5 allows an open redirect vulnerability that could lead to spoofing, aka "Microsoft Exchange Open Redirect Vulnerability".

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

## Which versions are affected by CVE-2017-8621?

It affects 1 product.


Products: Microsoft Exchange Server.

## How do I fix CVE-2017-8621?

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

## Is CVE-2017-8621 being exploited?

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

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

What it is: CVE-2017-8621 is a medium-severity vulnerability in Microsoft Exchange Server, published on 11 Jul 2017. 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-2017-8621 in the wild and no public exploit code.

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

## Sources

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

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