Cloud Foundry UAA accepts refresh token as access token on admin endpoints
Cloud Foundry UAA
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.cloudfoundry.identity:cloudfoundry-identity-server Maven |
|
|
Cloud Foundry UAA
| Product | Affected | Fixed in |
|---|---|---|
| org.cloudfoundry.identity:cloudfoundry-identity-server Maven |
|
|
4.12.44.19.2Cloud 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.
From the CVE record · dell
Cloud Foundry UAA incorrectly accepts a valid refresh token instead of an access token at administrative endpoints such as /Users and /Groups. Someone possessing a valid refresh token can authenticate to those endpoints for longer than an access token would allow; the token becomes invalid if the user or client is deleted or the user's groups are removed.
Engineers running Cloud Foundry UAA or the Maven package org.cloudfoundry.identity:cloudfoundry-identity-server in the affected 4.5, 4.7, 4.10, 4.12, or 4.19 version ranges should check their deployments.