An issue was discovered in Cloud Foundry Foundation cf-release (all versions prior to v279) and UAA (30.x versions prior to 30.6, 45.x versions prior to 45.4, 52.x versions prior to 52.1). In some cases, the UAA allows an authenticated user for a particular client to revoke client tokens for other users on the same client. This occurs only if the client is using opaque tokens or JWT tokens validated using the check_token endpoint. A malicious actor could cause denial of service.
Summary
AIIn affected cf-release and UAA versions, an authenticated user of a client can, in some cases, revoke other users’ tokens for that same client. This can cause denial of service, but only when the client uses opaque tokens or JWT tokens validated through the check_token endpoint.
Who should check
Teams running cf-release before v279, UAA 30.x before 30.6, 45.x before 45.4, or 52.x before 52.1, or affected versions of the Maven package org.cloudfoundry.identity:cloudfoundry-identity-server, should check their deployments.
What to do
- 1Upgrade cf-release to v279 or later, or UAA to 30.6, 45.4, or 52.1 as appropriate.
- 2Upgrade affected cloudfoundry-identity-server package versions to the applicable fixed version: 4.7.1, 4.5.3, or 3.20.1.