dbcve.org
Capi ReleaseApplication · Cloudfoundry

CVE-2017-8037

HIGH · 7.5 CVSS v3.0 Published 2017-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a path traversal vulnerability in Cloud Foundry's Cloud Controller API (CAPI) that allows authenticated Space Developers to read arbitrary files on the Cloud Controller VM through specially crafted requests. It's an incomplete fix for CVE-2017-8035, exploiting the same underlying file disclosure weakness.

MitigationUpgrade CAPI-release to version 1.38.0 or later, or cf-release to version 270 or later. Organizations that previously remediated CVE-2017-8035 should also apply this subsequent patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Capi ReleaseApplication
Affected:= 1.7.0= 1.8.0= 1.9.0= 1.10.0= 1.11.0= 1.12.0= 1.13.0= 1.14.0= 1.15.0= 1.16.0= 1.17.0= 1.18.0
Cf ReleaseApplication
Affected:= 245= 246= 247= 248= 249= 250= 251= 252= 253= 254= 255= 256

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check CAPI-release version
    Locate the CAPI-release version deployed in your Cloud Foundry environment. This is typically found in your deployment manifest, BOSH release information, or by querying the Cloud Foundry ops manager/elastic runtime metadata. Use 'bosh releases' or check your deployment configuration files.
    Affected if The installed CAPI-release version is 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.11.0, 1.12.0, 1.13.0, 1.14.0, 1.15.0, 1.16.0, 1.17.0, or 1.18.0
  2. Check cf-release version
    Locate the cf-release version deployed in your Cloud Foundry environment. This is typically found in your deployment manifest or BOSH release information. Use 'bosh releases' or check your deployment configuration files.
    Affected if The installed cf-release version is 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, or 256
  3. Verify Cloud Controller API accessibility
    Determine if your Cloud Controller API (CAPI) endpoint is accessible from untrusted networks or if it is properly network-segmented. Check your security group configurations and API endpoint exposure.
    Affected if The Cloud Controller API is externally accessible without strict network isolation from untrusted users
  4. Identify Space Developer access surface
    Review which users or service accounts have Space Developer roles in your Cloud Foundry organization and space structures. Check if external or untrusted entities can obtain Space Developer credentials.
    Affected if Untrusted or external users can obtain Space Developer role credentials in your Cloud Foundry deployment
  5. Confirm vulnerability is exploitable
    The path traversal vulnerability in the Cloud Controller API allows authenticated Space Developers to use specially crafted requests to access files outside the intended directory. The flaw exploits the same underlying file disclosure weakness as CVE-2017-8035 but represents an incomplete fix.
    Affected if Your environment meets all of the following: vulnerable CAPI or CF release version is deployed, the API is reachable by an authenticated Space Developer, and the attacker can send crafted requests to the Cloud Controller API

You are affected if your Cloud Foundry deployment uses CAPI-release versions 1.7.0-1.18.0 or cf-release versions 245-256 AND an authenticated Space Developer can access the Cloud Controller API endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CAPI-release to version 1.38.0 or later, or cf-release to version 270 or later. Organizations that previously remediated CVE-2017-8035 should also apply this subsequent patch.

Fix this in Capi Release Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8037 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data