CVE-2017-8047
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCloud Foundry router in routing-release versions before v0.163.0 and cf-release versions before v274 contains an open redirect vulnerability. Attackers can append specific character combinations to URLs to redirect users to malicious sites, enabling phishing attacks to steal credentials or sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 273<= 0.162.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed routing-release versionLocate your Cloud Foundry deployment manifest or BOSH deployment and find the version of the routing-release package. Check the releases section or the compiled package version for the gorouter component.Affected if The routing-release version is 0.162.0 or lower, or the version cannot be determined but the deployment predates the v0.163.0 release.
-
Identify installed cf-release versionLocate your Cloud Foundry deployment manifest or BOSH deployment and find the version of the cf-release package. Check the releases section or the version of the cf-deployment.Affected if The cf-release version is 273 or lower, or the version cannot be determined but the deployment predates the v274 release.
-
Verify router component is presentCheck that the gorouter (Cloud Foundry router) component is deployed and running in your environment. This is typically found in the routing-release or as part of the router job in cf-deployment.Affected if The router component is deployed and the version cannot be confirmed as patched.
-
Check router accessibilityDetermine if the Cloud Foundry router is accessible externally or to end users. Inspect network policies and the router's bound domains configuration.Affected if The router accepts external traffic and unauthenticated users can be redirected via crafted URLs.
You are affected if your deployment uses routing-release v0.162.0 or earlier, or cf-release v273 or earlier, and the router component is accessible to users who could be redirected to external sites.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to cf-release v274 (or v275 for the bug fix) and routing-release v0.163.0 or later. Validate all redirects in the application do not allow arbitrary external URLs.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-8047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data