# CVE-2016-6651: Privilege escalation in n/a

> Authenticated users can escalate privileges by leveraging a token in the UAA OAuth token endpoint of Pivotal Cloud Foundry.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 30 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-42fx-hqwh-j72r

## What is CVE-2016-6651?

CVE-2016-6651 is a high-severity vulnerability in n/a, published on 30 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The UAA /oauth/token endpoint in Pivotal Cloud Foundry (PCF) before 243; UAA 2.x before 2.7.4.8, 3.x before 3.3.0.6, and 3.4.x before 3.4.5; UAA BOSH before 11.7 and 12.x before 12.6; Elastic Runtime before 1.6.40, 1.7.x before 1.7.21, and 1.8.x before 1.8.2; and Ops Manager 1.7.x before 1.7.13 and 1.8.x before 1.8.1 allows remote authenticated users to gain privileges by leveraging possession of a token.

Weakness: CWE-264

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

It affects 5 products.


Products: Cloudfoundry Cloud Foundry Uaa Bosh, Pivotal Software Cloud Foundry, Pivotal Software Cloud Foundry Elastic Runtime, Pivotal Software Cloud Foundry Ops Manager, Pivotal Software Cloud Foundry Uaa.

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

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

## Is CVE-2016-6651 being exploited?

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

## Other vulnerabilities in n/a

- [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-3084](https://insights.sbomify.com/CVE-2016-3084/): Cloud Foundry UAA reset password vulnerable to brute force attack (high 8.1)
- [CVE-2016-6659](https://insights.sbomify.com/CVE-2016-6659/): Privilege escalation in Cloud Foundry v247 and earlier and UAA v3.9.2 & earlier and UAA bosh (uaa-release) v23 & earlier (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6651 is a high-severity vulnerability in n/a, published on 30 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6651 in the wild and no public exploit code.

Affected product: n/a. 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-6651/ (Markdown: https://insights.sbomify.com/CVE-2016-6651/index.md)
```

## Sources

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

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