CVE-2017-8035: Infoleak
First published: Tue Jul 25 2017(Updated: )
An issue was discovered in the Cloud Controller API in Cloud Foundry Foundation CAPI-release versions after v1.6.0 and prior to v1.35.0 and cf-release versions after v244 and prior to v268. 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.
Credit: security_alert@emc.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Cloud Foundry CAPI-release | >=1.7.0<1.35.0 | |
| Cloud Foundry CF Release | >=245<268 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-8035?
CVE-2017-8035 has been classified as a medium-severity vulnerability.
How do I fix CVE-2017-8035?
To fix CVE-2017-8035, update the Cloud Foundry CAPI-release to version 1.35.0 or later, or the CF Release to version 268 or later.
Who is affected by CVE-2017-8035?
CVE-2017-8035 affects users of Cloud Foundry CAPI-release versions between 1.7.0 and 1.35.0, and CF Release versions between 245 and 268.
What is the impact of CVE-2017-8035?
The impact of CVE-2017-8035 allows unauthorized file access for Space Developers through a crafted CAPI request.
When was CVE-2017-8035 disclosed?
CVE-2017-8035 was disclosed in 2017 as part of ongoing security assessments of the Cloud Foundry platform.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/author
- agent/weakness
- agent/references
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/cloudfoundry
- canonical/cloud foundry capi-release
- version/cloud foundry capi-release/1.7.0
- canonical/cloud foundry cf release
- version/cloud foundry cf release/245