In Cloud Foundry Foundation cf-release versions prior to v285; cf-deployment versions prior to v1.7; UAA 4.5.x versions prior to 4.5.5, 4.8.x versions prior to 4.8.3, and 4.7.x versions prior to 4.7.4; and UAA-release 45.7.x versions prior to 45.7, 52.7.x versions prior to 52.7, and 53.3.x versions prior to 53.3, the SessionID is logged in audit event logs. An attacker can use the SessionID to impersonate a logged-in user.
Summary
AIAffected Cloud Foundry components log SessionIDs in audit event logs. An attacker who obtains a logged SessionID can use it to impersonate a logged-in user; the input does not specify whether accessing the logs requires authentication or user interaction.
Who should check
Operators of cf-release before v285, cf-deployment before v1.7, the listed affected UAA and UAA-release versions, and users of affected Maven org.cloudfoundry.identity:cloudfoundry-identity-server versions should check their deployments.
What to do
- 1Update cf-release to v285 and cf-deployment to v1.7; update affected UAA branches to 4.5.5, 4.7.4, or 4.8.3, and affected UAA-release branches to 45.7, 52.7, or 53.3.
- 2Update affected Maven org.cloudfoundry.identity:cloudfoundry-identity-server branches to 4.5.5, 4.7.4, or 4.8.3, respectively.