CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2016 · Cloudfoundry

CVE-2016-6658
Cloudfoundry Cf-release vulnerability

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.

Affected products

Cf-release, Cloud Foundry Elastic Runtime. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Cloudfoundry Cf-release runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Cloudfoundry products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.