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
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.2, 4.12.4, 4.10.2, 4.7.6, 4.5.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Cloud Foundry Cloud Foundry UAA
From 4.19 · fixed in 4.19.2; From 4.12 · fixed in 4.12.4; From 4.10 · fixed in 4.10.2; From 4.7 · fixed in 4.7.6; From 4.5 · fixed in 4.5.7
- org.cloudfoundry.identity:cloudfoundry-identity-serverMaven
fixed in 4.5.7
- org.cloudfoundry.identity:cloudfoundry-identity-serverMaven
From 4.6.0 · fixed in 4.7.6
- org.cloudfoundry.identity:cloudfoundry-identity-serverMaven
From 4.8.0 · fixed in 4.10.2
- org.cloudfoundry.identity:cloudfoundry-identity-serverMaven
From 4.11.0 · fixed in 4.12.4
- org.cloudfoundry.identity:cloudfoundry-identity-serverMaven
From 4.13.0 · fixed in 4.19.2