Vulnerability in Cloud Foundry capi-release (CVE-2017-8048)
Summary
Vulnerability in Cloud Foundry capi-release (CVE-2017-8048). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 275 or later.
Original description
The description as published by the source.
In Cloud Foundry capi-release versions 1.33.0 and later, prior to 1.42.0 and cf-release versions 268 and later, prior to 274, the original fix for CVE-2017-8033 introduces an API regression that allows a space developer to execute arbitrary code on the Cloud Controller VM by pushing a specially crafted application. 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-8048 has been found in Cloud Foundry capi-release.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade Cloud Foundry capi-release to 275 or later.
If unsure, ask your IT team or search "Cloud Foundry capi-release CVE-2017-8048" on the vendor's site.
CVE-2017-8048 (Cloud Foundry capi-release) — CVSS v3 7.8
Attack vector: local / 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 (unclassified) exists in Cloud Foundry capi-release.
Check the vendor advisory for the affected versions of Cloud Foundry capi-release.
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover.
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 capi-release を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Cloud Foundry capi-release to 275ステージング環境で 275 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory cloudfoundry.org