CVE-2018-11083: Bosh accepts refresh tokens in place of an access token
Cloud Foundry BOSH, versions v264 prior to v264.14.0 and v265 prior to v265.7.0 and v266 prior to v266.8.0 and v267 prior to v267.2.0, allows refresh tokens to be as access tokens when using UAA for authentication. A remote attacker with an admin refresh token given by UAA can be used to access BOSH resources without obtaining an access token, even if their user no longer has access to those resources.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2018-11083?
CVE-2018-11083 has been rated as a high severity vulnerability due to the potential for remote exploitation.
How do I fix CVE-2018-11083?
To fix CVE-2018-11083, upgrade your Cloud Foundry BOSH to version 264.14.0 or later, 265.7.0 or later, 266.8.0 or later, or 267.2.0 or later.
What types of systems are affected by CVE-2018-11083?
CVE-2018-11083 affects Cloud Foundry BOSH in various versions prior to the specified fixed versions.
What can an attacker do if they exploit CVE-2018-11083?
If exploited, an attacker can use a refresh token as an access token, gaining unauthorized access to resources.
Is there a workaround for CVE-2018-11083?
Currently, applying the recommended updates is the best method to mitigate CVE-2018-11083 as no official workaround is provided.