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.
References
Link | Resource |
---|---|
https://pivotal.io/security/cve-2016-6658 | Vendor Advisory |
https://pivotal.io/security/cve-2016-6658 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
History
21 Nov 2024, 02:56
Type | Values Removed | Values Added |
---|---|---|
References | () https://pivotal.io/security/cve-2016-6658 - Vendor Advisory |
Information
Published : 2018-03-29 22:29
Updated : 2024-11-21 02:56
NVD link : CVE-2016-6658
Mitre link : CVE-2016-6658
CVE.ORG link : CVE-2016-6658
JSON object : View
Products Affected
cloudfoundry
- cf-release
pivotal_software
- cloud_foundry_elastic_runtime
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor