# CVE-2016-6877: Open redirect in n/a

> Man-in-the-middle attackers can trigger HTTP 302 redirections via the Host header, though the vendor disputes validity due to TLS requirements.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/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:** 5 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g7jr-3gjx-fr4f

## What is CVE-2016-6877?

CVE-2016-6877 is a medium-severity vulnerability in n/a, published on 5 May 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

Citrix XenMobile Server before 10.5.0.24 allows man-in-the-middle attackers to trigger HTTP 302 redirections via vectors involving the HTTP Host header and a cached page.  NOTE: the vendor reports "our internal analysis of this issue concluded that this was not a valid vulnerability" because an exploitation scenario would involve a man-in-the-middle attack against a TLS session

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-6877?

It affects 1 product.


Products: Citrix Xenmobile Server.

## How do I fix CVE-2016-6877?

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

## Is CVE-2016-6877 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8211](https://insights.sbomify.com/CVE-2020-8211/): SQL injection in Citrix XenMobile Server (critical 9.8)
- [CVE-2020-8212](https://insights.sbomify.com/CVE-2020-8212/): Missing authorization in Citrix XenMobile Server (critical 9.8)
- [CVE-2018-10648](https://insights.sbomify.com/CVE-2018-10648/): File upload in n/a (critical 9.8)
- [CVE-2018-10653](https://insights.sbomify.com/CVE-2018-10653/): XML external entity in n/a (critical 9.8)
- [CVE-2018-18571](https://insights.sbomify.com/CVE-2018-18571/): Auth bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6877 and fix it if it is affected.

What it is: CVE-2016-6877 is a medium-severity vulnerability in n/a, published on 5 May 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-2016-6877 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-2016-6877/ (Markdown: https://insights.sbomify.com/CVE-2016-6877/index.md)
```

## Sources

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

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