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.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Cloud_foundry_uaa | Pivotal_software | 4.5.0 (including) | 4.5.7 (excluding) |
Cloud_foundry_uaa | Pivotal_software | 4.7.0 (including) | 4.7.6 (excluding) |
Cloud_foundry_uaa | Pivotal_software | 4.10.0 (including) | 4.10.2 (excluding) |
Cloud_foundry_uaa | Pivotal_software | 4.12.0 (including) | 4.12.4 (excluding) |
Cloud_foundry_uaa | Pivotal_software | 4.19.0 (including) | 4.19.2 (excluding) |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.