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.
Subscriptions
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2016-7561 | 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. |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://pivotal.io/security/cve-2016-6658 |
|
History
No history.
Status: PUBLISHED
Assigner: dell
Published:
Updated: 2024-08-06T01:36:29.571Z
Reserved: 2016-08-10T00:00:00.000Z
Link: CVE-2016-6658
No data.
Status : Modified
Published: 2018-03-29T22:29:00.477
Modified: 2024-11-21T02:56:34.143
Link: CVE-2016-6658
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD