# CVE-2018-1262: UAA privilege escalation across identity zones

> A zone administrator can configure tokens to impersonate another zone, granting admin privileges in the impersonated zone for clients using offline validation.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8v97-gv3g-32rf

## What is CVE-2018-1262?

CVE-2018-1262 is a high-severity vulnerability in CloudFoundry UAA, published on 15 May 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cloud Foundry Foundation UAA, versions 4.12.X and 4.13.X, introduced a feature which could allow privilege escalation across identity zones for clients performing offline validation. A zone administrator could configure their zone to issue tokens which impersonate another zone, granting up to admin privileges in the impersonated zone for clients performing offline token validation.

## Which versions are affected by CVE-2018-1262?

4 open source packages ship an affected version, including org.cloudfoundry.identity:cloudfoundry-identity-server. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.cloudfoundry.identity:cloudfoundry-identity-server` | Maven | From 4.12.0 | 4.12.2 |
| `org.cloudfoundry.identity:cloudfoundry-identity-server` | Maven | From 4.12.0 | 4.12.2 |
| `org.cloudfoundry.identity:cloudfoundry-identity-server` | Maven | From 4.13.0 | 4.13.4 |
| `org.cloudfoundry.identity:cloudfoundry-identity-server` | Maven | From 4.13.0 | 4.13.4 |

Products: Cloudfoundry Cf-Deployment, Pivotal Software Cloud Foundry Uaa, Pivotal Software Cloud Foundry Uaa-Release.

## How do I fix CVE-2018-1262?

Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to a fixed version for your release line: 4.12.2 or 4.13.4.

## Is CVE-2018-1262 being exploited?

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

## Other vulnerabilities in CloudFoundry UAA

- [CVE-2022-31733](https://insights.sbomify.com/CVE-2022-31733/): Auth bypass in Cloud Foundry Diego and CF Deployment (critical 9.1)
- [CVE-2020-5402](https://insights.sbomify.com/CVE-2020-5402/): UAA fails to check the state parameter when authenticating with external IDPs (high 8.8)
- [CVE-2019-11293](https://insights.sbomify.com/CVE-2019-11293/): UAA logs all query parameters with debug logging level (high 8.8)
- [CVE-2019-11290](https://insights.sbomify.com/CVE-2019-11290/): Cloud Foundry UAA logs query parameters in tomcat access file (high 8.8)
- [CVE-2019-11283](https://insights.sbomify.com/CVE-2019-11283/): Password leak in smbdriver logs (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1262 and fix it if it is affected.

What it is: CVE-2018-1262 is a high-severity vulnerability in CloudFoundry UAA, published on 15 May 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1262 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.cloudfoundry.identity:cloudfoundry-identity-server (Maven): affected from 4.12.0; fixed in 4.12.2
- org.cloudfoundry.identity:cloudfoundry-identity-server (Maven): affected from 4.12.0; fixed in 4.12.2
- org.cloudfoundry.identity:cloudfoundry-identity-server (Maven): affected from 4.13.0; fixed in 4.13.4
- org.cloudfoundry.identity:cloudfoundry-identity-server (Maven): affected from 4.13.0; fixed in 4.13.4

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-2018-1262/ (Markdown: https://insights.sbomify.com/CVE-2018-1262/index.md)
```

## Sources

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

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