CVE-2018-11047: UAA accepts refresh token as access token on admin endpoints
Cloud Foundry Foundation
Affected Cloud Foundry Products and Versions
- You are using uaa versions 4.19 prior to 4.19.2, 4.12 prior to 4.12.4, 4.10 prior to 4.10.2, 4.7 prior to 4.7.6, 4.5 prior to 4.5.7
- You are using uaa-release versions v60 prior to v60.2, v57 prior to v57.4, v55 prior to v55.2, v52 prior to v52.10, v45 prior to v45.11
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.
Users of affected versions should apply the following mitigations or upgrades:
- Releases that have fixed this issue include:
- uaa versions 4.19.2, 4.12.4, 4.10.2, 4.7.6, 4.5.7
- uaa-release versions v60.2, v57.4, v55.2, v52.10, v45.11
This issue was responsibly reported by Dr. Nic Williams, Stark and Wayne.
2018-07-18: Initial vulnerability report published.