# Cloud Foundry UAA accepts refresh token as access token on admin endpoints

Advisory record · `GHSA-r4v8-9hgx-vm6m`

- **Identifiers:** `GHSA-r4v8-9hgx-vm6m` · `CVE-2018-11047`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 13 May 2022
- **Updated:** 1 Mar 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2022, 01:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.cloudfoundry.identity:cloudfoundry-identity-server` (Maven): affected `<4.5.7 || >=4.6.0, <4.7.6 || >=4.8.0, <4.10.2 || >=4.11.0, <4.12.4 || >=4.13.0, <4.19.2`; fixed in `4.5.7`, `4.7.6`, `4.10.2`, `4.12.4`, `4.19.2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 65th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 13 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-r4v8-9hgx-vm6m](https://github.com/advisories/GHSA-r4v8-9hgx-vm6m)
- [OSV: GHSA-r4v8-9hgx-vm6m](https://osv.dev/vulnerability/GHSA-r4v8-9hgx-vm6m)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-11047>
- <https://github.com/cloudfoundry/uaa/commit/0cd3c6fdd96206a1d6a376ac62e21e59e16cdcb1>
- <https://github.com/cloudfoundry/uaa/commit/2906057dae995024576ce6afdc20abd85569514>
- <https://github.com/cloudfoundry/uaa/commit/4cb1be404cf4a82e39cf2a6357aa17af8b33f2a1>
- <https://github.com/cloudfoundry/uaa/commit/4fa3e351ec0bface3b693810605905e29a9a8569>
- <https://github.com/cloudfoundry/uaa/commit/5d021e83ef143c64179d0da015aa76321ee40988>
- <https://github.com/cloudfoundry/uaa/commit/81aeb7a3aa048ea086c494f725d643e48dd9266>
- <https://github.com/cloudfoundry/uaa/commit/a1d523c7f150e56bf06df8b83ed1d416d6c1d3b>
- <https://github.com/cloudfoundry/uaa/commit/aba1fb5f18e0d628628b2d960fc6d0cc62d86f5>
- <https://github.com/cloudfoundry/uaa/commit/b37552d2bf084de059bc965b5ef5a45e64883904>
- <https://github.com/cloudfoundry/uaa/commit/bbbba5aec514ad88e7d1e168a2519c80229f02f>
- <https://github.com/cloudfoundry/uaa>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r4v8-9hgx-vm6m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r4v8-9hgx-vm6m/>. Everything for agents: <https://agentprime.io/llms.txt>.
