# CVE-2017-8048: Code injection in Cloud Controller VM capi-release versions 1.33.0 and later, prior to 1.42.0, cf-release versions 268 and later, prior to 274

> A space developer can execute arbitrary code on the Cloud Controller VM by pushing a specially crafted application due to an API regression.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **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-9j8m-7rpr-659f

## What is CVE-2017-8048?

CVE-2017-8048 is a high-severity code injection vulnerability in Cloud Controller VM capi-release versions 1.33.0 and later, prior to 1.42.0, cf-release versions 268 and later, prior to 274, published on 3 Oct 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

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

It affects 2 products.


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

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

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

## Is CVE-2017-8048 being exploited?

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

## Other vulnerabilities in Cloud Controller VM capi-release versions 1.33.0 and later, prior to 1.42.0, cf-release versions 268 and later, prior to 274

- [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-8048 and fix it if it is affected.

What it is: CVE-2017-8048 is a high-severity code injection vulnerability in Cloud Controller VM capi-release versions 1.33.0 and later, prior to 1.42.0, cf-release versions 268 and later, prior to 274, published on 3 Oct 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8048 in the wild and no public exploit code.

Affected product: Cloud Controller VM capi-release versions 1.33.0 and later, prior to 1.42.0, cf-release versions 268 and later, prior to 274. 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-8048/ (Markdown: https://insights.sbomify.com/CVE-2017-8048/index.md)
```

## Sources

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

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