Applications in cf-release before 245 can be configured and pushed with a user-provided custom buildpack using a URL pointing to the buildpack. Although it is not recommended, a user can specify a credential in the URL (basic auth or OAuth) to access the buildpack through the CLI. For example, the user could include a GitHub username and password in the URL to access a private repo. Because the URL to access the buildpack is stored unencrypted, an operator with privileged access to the Cloud Controller database could view these credentials.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NCloudfoundry Cf Release
APPCloudfoundry< 245Pivotal Software Cloud Foundry Elastic Runtime
APPPivotal Software< 1.6.491.7.0 – 1.7.31 (excl.)1.8.0 – 1.8.11 (excl.)
Related vulnerabilities
Cloud Foundry: brak unieważniania sesji po zmianie hasła
Cloud Foundry: brak wygasania linków resetowania hasła
Cloud Foundry: Podszywanie się pod użytkowników przez błąd walidacji JWT
Command injection w skryptach Cloud Foundry i cf-mysql-release
Pivotal PCF Elastic Runtime — podszywanie się pod użytkowników przez błąd walidacji JWT