Open Redirect in Cloud Foundry router routing-release all (CVE-2017-8047)
Summary
Vulnerability in Cloud Foundry router routing-release all (CVE-2017-8047). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 275 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2017-8047 has been found in Cloud Foundry router routing-release all.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade Cloud Foundry router routing-release all to 275 or later.
If unsure, ask your IT team or search "Cloud Foundry router routing-release all CVE-2017-8047" on the vendor's site.
CVE-2017-8047 (Cloud Foundry router routing-release all) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 275 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in Cloud Foundry router routing-release all.
Check the vendor advisory for the affected versions of Cloud Foundry router routing-release all.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 275.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Cloud Foundry router routing-release all を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Cloud Foundry router routing-release all to 275ステージング環境で 275 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory cloudfoundry.org