CVE-2018-11047

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2018-11047 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.5.7, 4.7.6, 4.10.2, 4.12.4, 4.19.2); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2018-11047? CVE-2018-11047 is a high-severity incorrect authorization vulnerability in org.cloudfoundry.identity:cloudfoundry-identity-server (maven), affecting versions < 4.5.7. It is fixed in 4.5.7, 4.7.6, 4.10.2, 4.12.4, 4.19.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2018-11047? CVE-2018-11047 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.cloudfoundry.identity:cloudfoundry-identity-server are affected by CVE-2018-11047? org.cloudfoundry.identity:cloudfoundry-identity-server (maven) versions < 4.5.7 is affected.
4. Is there a fix for CVE-2018-11047? Yes. CVE-2018-11047 is fixed in 4.5.7, 4.7.6, 4.10.2, 4.12.4, 4.19.2. Upgrade to this version or later.
5. Is CVE-2018-11047 exploitable, and should I be worried? Whether CVE-2018-11047 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2018-11047 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2018-11047?
   • Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to 4.5.7 or later
   • Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to 4.7.6 or later
   • Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to 4.10.2 or later
   • Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to 4.12.4 or later
   • Upgrade org.cloudfoundry.identity:cloudfoundry-identity-server to 4.19.2 or later