# CVE-2016-4435: Missing authorization in Cloud Foundry

> Unauthenticated attackers can read or write blobs and cause denial of service on BOSH Director VMs by guessing GUIDs.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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:** 6 Aug 2024
- **Also known as:** GHSA-3rx5-2rm5-fvhx

## What is CVE-2016-4435?

CVE-2016-4435 is a critical missing authorization 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

An endpoint of the Agent running on the BOSH Director VM with stemcell versions prior to 3232.6 and 3146.13 may allow unauthenticated clients to read or write blobs or cause a denial of service attack on the Director VM. This vulnerability requires that the unauthenticated clients guess or find a URL matching an existing GUID.

Weakness: CWE-264

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

It affects 1 product.


Products: Pivotal Bosh Stemcell.

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

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

## Is CVE-2016-4435 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4435 is a critical missing authorization 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-4435 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-4435/ (Markdown: https://insights.sbomify.com/CVE-2016-4435/index.md)
```

## Sources

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

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