Skip to content

Cloud Foundry UAA accepts refresh token as access token on admin endpoints

High severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Mar 1, 2024

Package

maven org.cloudfoundry.identity:cloudfoundry-identity-server (Maven)

Affected versions

< 4.5.7
>= 4.6.0, < 4.7.6
>= 4.8.0, < 4.10.2
>= 4.11.0, < 4.12.4
>= 4.13.0, < 4.19.2

Patched versions

4.5.7
4.7.6
4.10.2
4.12.4
4.19.2

Description

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.

References

Published by the National Vulnerability Database Jul 24, 2018
Published to the GitHub Advisory Database May 13, 2022
Reviewed Mar 1, 2024
Last updated Mar 1, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.085%
(37th percentile)

Weaknesses

CVE ID

CVE-2018-11047

GHSA ID

GHSA-r4v8-9hgx-vm6m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.