# CVE-2016-6659: Privilege escalation in Cloud Foundry v247 and earlier and UAA v3.9.2 & earlier and UAA bosh (uaa-release) v23 & earlier

> Attackers can escalate privileges by accessing UAA logs and interacting with a SAML provider, affecting Cloud Foundry deployments.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/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:** 23 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8pj8-jjrc-8g8h

## What is CVE-2016-6659?

CVE-2016-6659 is a high-severity vulnerability in Cloud Foundry v247 and earlier and UAA v3.9.2 & earlier and UAA bosh (uaa-release) v23 & earlier, published on 23 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cloud Foundry before 248; UAA 2.x before 2.7.4.12, 3.x before 3.6.5, and 3.7.x through 3.9.x before 3.9.3; and UAA bosh release (aka uaa-release) before 13.9 for UAA 3.6.5 and before 24 for UAA 3.9.3 allow attackers to gain privileges by accessing UAA logs and subsequently running a specially crafted application that interacts with a configured SAML provider.

Weakness: CWE-287 (Improper Authentication)

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

It affects 3 products.


Products: Cloudfoundry Cloud Foundry Uaa Bosh, Pivotal Software Cloud Foundry, Pivotal Software Cloud Foundry Uaa.

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

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

## Is CVE-2016-6659 being exploited?

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

## Other vulnerabilities in Cloud Foundry v247 and earlier and UAA v3.9.2 & earlier and UAA bosh (uaa-release) v23 & earlier

- [CVE-2016-6637](https://insights.sbomify.com/CVE-2016-6637/): Cloud Foundry vulnerable to Cross-Site Request Forgery (critical 9.6)
- [CVE-2017-4973](https://insights.sbomify.com/CVE-2017-4973/): Cloud Foundry UAA Privilege Escalation (high 8.8)
- [CVE-2016-4468](https://insights.sbomify.com/CVE-2016-4468/): SQL injection in n/a (high 8.8)
- [CVE-2016-6651](https://insights.sbomify.com/CVE-2016-6651/): Privilege escalation in n/a (high 8.8)
- [CVE-2016-3084](https://insights.sbomify.com/CVE-2016-3084/): Cloud Foundry UAA reset password vulnerable to brute force attack (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6659 is a high-severity vulnerability in Cloud Foundry v247 and earlier and UAA v3.9.2 & earlier and UAA bosh (uaa-release) v23 & earlier, published on 23 Dec 2016. 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-6659 in the wild and no public exploit code.

Affected product: Cloud Foundry v247 and earlier and UAA v3.9.2 & earlier and UAA bosh (uaa-release) v23 & earlier. 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-6659/ (Markdown: https://insights.sbomify.com/CVE-2016-6659/index.md)
```

## Sources

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

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