CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2017 · Cloudfoundry

CVE-2017-8037
Cloudfoundry Capi-release vulnerability

In Cloud Foundry Foundation CAPI-release versions after v1.6.0 and prior to v1.38.0 and cf-release versions after v244 and prior to v270, there is an incomplete fix for CVE-2017-8035. If you took steps to remediate CVE-2017-8035 you should also upgrade to fix this CVE. A carefully crafted CAPI request from a Space Developer can allow them to gain access to files on the Cloud Controller VM for that installation, aka an Information Leak / Disclosure.

Affected products

Capi-release, Cf-release. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Cloudfoundry Capi-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.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

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.