CVE-2018-11047: Cloud Foundry UAA accepts refresh token as access token on admin endpoints
7.5
CVSS Score
3.0
Basic Information
CVE ID
GHSA ID
EPSS Score
0.50899%
CWE
Published
5/13/2022
Updated
3/1/2024
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
org.cloudfoundry.identity:cloudfoundry-identity-server | maven | < 4.5.7 | 4.5.7 |
org.cloudfoundry.identity:cloudfoundry-identity-server | maven | >= 4.6.0, < 4.7.6 | 4.7.6 |
org.cloudfoundry.identity:cloudfoundry-identity-server | maven | >= 4.8.0, < 4.10.2 | 4.10.2 |
org.cloudfoundry.identity:cloudfoundry-identity-server | maven | >= 4.11.0, < 4.12.4 | 4.12.4 |
org.cloudfoundry.identity:cloudfoundry-identity-server | maven | >= 4.13.0, < 4.19.2 | 4.19.2 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stemmed from UAA's failure to distinguish between access tokens and refresh tokens when authorizing admin endpoints. The patch added JTI claim validation in loadAuthentication() to reject tokens ending with REFRESH_TOKEN_SUFFIX. The pre-patch version of this function lacked these checks, making it the root cause. Multiple test cases in UaaTokenServicesTests.java confirm this was the vulnerable entry point by testing refresh token rejection scenarios.