Bosh accepts refresh tokens in place of an access token
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cloud Foundry | BOSH | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2018-3127 | 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. |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 1.5% (1.483% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://www.cloudfoundry.org/blog/cve-2018-11083 |
|
No history.