# CVE-2016-0761: Path traversal in Cloud Foundry

> Attackers can delete, corrupt, or overwrite host files and other container filesystems via flawed Docker image preparation in Cloud Foundry Garden-Linux.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2c5j-c3wx-m67f

## What is CVE-2016-0761?

CVE-2016-0761 is a critical path traversal vulnerability in Pivotal Cloud Foundry, published on 25 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cloud Foundry Garden-Linux versions prior to v0.333.0 and Elastic Runtime 1.6.x version prior to 1.6.17 contain a flaw in managing container files during Docker image preparation that could be used to delete, corrupt or overwrite host files and directories, including other container filesystems on the host.

Weakness: CWE-19

## Which versions are affected by CVE-2016-0761?

It affects 2 products.


Products: Cloudfoundry Garden Linux, Pivotal Software Cloud Foundry Elastic Runtime.

## How do I fix CVE-2016-0761?

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

## Is CVE-2016-0761 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0761 and fix it if it is affected.

What it is: CVE-2016-0761 is a critical path traversal vulnerability in Pivotal Cloud Foundry, published on 25 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-0761 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-2016-0761/ (Markdown: https://insights.sbomify.com/CVE-2016-0761/index.md)
```

## Sources

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

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