Cloud Foundry UAA, versions 4.19 prior to 4.19.2 and 4.12 prior to 4.12.4 and 4.10 prior to 4.10.2 and 4.7 prior to 4.7.6 and 4.5 prior to 4.5.7, incorrectly authorizes requests to admin endpoints by accepting a valid refresh token in lieu of an access token. Refresh tokens by design have a longer expiration time than access tokens, allowing the possessor of a refresh token to authenticate longer than expected. This affects the administrative endpoints of the UAA. i.e. /Users, /Groups, etc. However, if the user has been deleted or had groups removed, or the client was deleted, the refresh token will no longer be valid.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| pivotal_software | cloud_foundry_uaa | 4.5.0 - 4.5.7 | - |
| pivotal_software | cloud_foundry_uaa | 4.7.0 - 4.7.6 |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
5
Affected Products
2
References
pivotal_software / cloud_foundry_uaa
| - |
| pivotal_software | cloud_foundry_uaa | 4.10.0 - 4.10.2 | - |
| pivotal_software | cloud_foundry_uaa | 4.12.0 - 4.12.4 | - |
| pivotal_software | cloud_foundry_uaa | 4.19.0 - 4.19.2 | - |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploitability
Impact