# CVE-2017-1000163: Phoenix Arbitrary URL Redirect

> Attackers can redirect users to malicious sites via unvalidated URLs, facilitating phishing attacks against Phoenix Framework applications.

- **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:** Yes
- **Published:** 17 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cmfh-8f8r-fj96

## What is CVE-2017-1000163?

CVE-2017-1000163 is a medium-severity vulnerability in n/a, published on 17 Nov 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

The Phoenix Framework versions 1.0.0 through 1.0.4, 1.1.0 through 1.1.6, 1.2.0, 1.2.2 and 1.3.0-rc.0 are vulnerable to unvalidated URL redirection, which may result in phishing or social engineering attacks.

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

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

6 open source packages ship an affected version, including phoenix. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `phoenix` | Hex | All versions | 1.0.6 |
| `phoenix` | Hex | All versions | 1.0.6 |
| `phoenix` | Hex | From 1.1.0 | 1.1.8 |
| `phoenix` | Hex | From 1.1.0 | 1.1.8 |
| `phoenix` | Hex | From 1.2.0 | 1.2.3 |
| `phoenix` | Hex | From 1.2.0 | 1.2.3 |

Products: Phoenixframework Phoenix.

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

Upgrade phoenix to a fixed version for your release line: 1.0.6, 1.1.8 or 1.2.3.

## Is CVE-2017-1000163 being exploited?

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

Public exploit code:

- Phoenix Framework - Open Redirect (nuclei): http/cves/2017/CVE-2017-1000163.yaml

## Other vulnerabilities in n/a

- [CVE-2026-56811](https://insights.sbomify.com/CVE-2026-56811/): Phoenix transports do not limit channel joins per connection, enabling process-exhaustion denial of service (high 8.7)
- [CVE-2022-42975](https://insights.sbomify.com/CVE-2022-42975/): Phoenix before 1.6.14 mishandles check_origin wildcarding (high 7.5)
- [CVE-2026-56812](https://insights.sbomify.com/CVE-2026-56812/): Phoenix: Presence keys colliding with `Object.prototype` members break existence checks (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000163 and fix it if it is affected.

What it is: CVE-2017-1000163 is a medium-severity vulnerability in n/a, published on 17 Nov 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000163 exists.

Affected packages and fixed versions:
- phoenix (Hex): affected all versions; fixed in 1.0.6
- phoenix (Hex): affected all versions; fixed in 1.0.6
- phoenix (Hex): affected from 1.1.0; fixed in 1.1.8
- phoenix (Hex): affected from 1.1.0; fixed in 1.1.8
- phoenix (Hex): affected from 1.2.0; fixed in 1.2.3
- phoenix (Hex): affected from 1.2.0; fixed in 1.2.3

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

## Sources

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

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