VDB

CVE-2017-8037

CVE-2017-8037 PUBLISHED

Reported by dell · Published August 21, 2017

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

VendorProductVersions
n/aCloud FoundryCloud Foundry
n/aCloud Foundry*

Timeline

  • Aug 21, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Apr 6, 2026 Security Advisory
  • Jun 17, 2026 CVE Updated
  • Sep 27, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-8037
vulnetix vdb fixes CVE-2017-8037

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-8037/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_CONFIRM
  • 100448 vdb-entryx_refsource_BID
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›