# CVE-2015-1834: Path traversal in Cloud Foundry

> Remote authenticated attackers can exploit path traversal in Cloud Foundry Cloud Controller to upload arbitrary files outside the application container, potentially leading to code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xmcg-5rvr-g4j6

## What is CVE-2015-1834?

CVE-2015-1834 is a medium-severity path traversal vulnerability in Pivotal Cloud Foundry, published on 25 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A path traversal vulnerability was identified in the Cloud Foundry component Cloud Controller that affects cf-release versions prior to v208 and Pivotal Cloud Foundry Elastic Runtime versions prior to 1.4.2. Path traversal is the 'outbreak' of a given directory structure through relative file paths in the user input. It aims at accessing files and directories that are stored outside the web root folder, for disallowed reading or even executing arbitrary system commands. An attacker could use a certain parameter of the file path for instance to inject '../' sequences in order to navigate through the file system. In this particular case a remote authenticated attacker can exploit the identified vulnerability in order to upload arbitrary files to the server running a Cloud Controller instance - outside the isolated application container.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2015-1834?

It affects 2 products.


Products: Cloudfoundry Cf-Release, Pivotal Software Cloud Foundry Elastic Runtime.

## How do I fix CVE-2015-1834?

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

## Is CVE-2015-1834 being exploited?

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

## Other vulnerabilities in Pivotal Cloud Foundry

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

What it is: CVE-2015-1834 is a medium-severity path traversal vulnerability in Pivotal Cloud Foundry, published on 25 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-1834 in the wild and no public exploit code.

Affected product: Pivotal Cloud Foundry. 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-2015-1834/ (Markdown: https://insights.sbomify.com/CVE-2015-1834/index.md)
```

## Sources

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

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