CVE-2017-1000163 — phoenix
MEDIUMCVE-2017-1000163 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in phoenix. A fix is available for phoenix — see the affected versions and patch details below.
Phoenix Arbitrary URL Redirect
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2017-1000163 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
phoenix💧phoenix💧phoenixReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💧Hex | phoenix | all versions | 1.0.6mix deps.update phoenix |
| 💧Hex | phoenix | ≥ 1.1.0&&< 1.1.8 | 1.1.8mix deps.update phoenix |
| 💧Hex | phoenix | ≥ 1.2.0&&< 1.2.3 | 1.2.3mix deps.update phoenix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for phoenix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update phoenix to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000163 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2017-1000163 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2017-1000163. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2017-1000163
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2017-1000163 -u https://target- Template
- Phoenix Framework - Open Redirect
- Severity
- medium
- Impact
- An attacker can craft a malicious URL that redirects users to a malicious website, leading to potential phishing attacks.
- Remediation
- Apply the latest security patches or upgrade to a patched version of the Phoenix Framework.
Template by ProjectDiscovery nuclei-templates (0x_Akoko), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2017-1000163 in your dependencies?
O3 Security finds CVE-2017-1000163 across Hex dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.