# CVE-2017-8047: Open redirect in Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274

> An open redirect in Cloud Foundry router allows attackers to redirect users to malicious sites, potentially leading to credential theft or data exposure.

- **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:** 3 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-398j-r5c5-vrph

## What is CVE-2017-8047?

CVE-2017-8047 is a medium-severity vulnerability in Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274, published on 3 Oct 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

In Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274, in some applications, it is possible to append a combination of characters to the URL that will allow for an open redirect. An attacker could exploit this as a phishing attack to gain access to user credentials or other sensitive data. NOTE: 274 resolves the vulnerability but has a serious bug that is fixed in 275.

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

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

It affects 2 products.


Products: Cloudfoundry Cf-Release, Pivotal Routing-Release.

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

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

## Is CVE-2017-8047 being exploited?

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

## Other vulnerabilities in Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274

- [CVE-2015-5171](https://insights.sbomify.com/CVE-2015-5171/): Cloud Foundry Runtime Insufficient Session Expiration vulnerability (critical 9.8)
- [CVE-2015-5172](https://insights.sbomify.com/CVE-2015-5172/): Cloud Foundry Runtime has Weak Password Recovery Mechanism for Forgotten Password (critical 9.8)
- [CVE-2016-8218](https://insights.sbomify.com/CVE-2016-8218/): Auth bypass in Cloud Foundry (critical 9.8)
- [CVE-2017-4992](https://insights.sbomify.com/CVE-2017-4992/): Cloud Foundry UAA privilege escalation with user invitations (critical 9.8)
- [CVE-2016-6658](https://insights.sbomify.com/CVE-2016-6658/): Information disclosure in n/a (critical 9.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8047 is a medium-severity vulnerability in Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274, published on 3 Oct 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-8047 in the wild and no public exploit code.

Affected product: Cloud Foundry router routing-release all versions prior to v0.163.0 and cf-release all versions prior to v274. 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-8047/ (Markdown: https://insights.sbomify.com/CVE-2017-8047/index.md)
```

## Sources

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

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