CVE-2017-8037
No exploitation reported by the sources we read.
- Published2017-08-21
- WeaknessCWE-200
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2017-08-2122:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-8037?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-8037?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.7 | = 1.7.0 | no fix published | NVD |
| 1.8 | = 1.8.0 | no fix published | NVD |
| 1.9 | = 1.9.0 | no fix published | NVD |
| 1.10 | = 1.10.0 | no fix published | NVD |
| 1.11 | = 1.11.0 | no fix published | NVD |
| 1.12 | = 1.12.0 | no fix published | NVD |
| 1.13 | = 1.13.0 | no fix published | NVD |
| 1.14 | = 1.14.0 | no fix published | NVD |
| 1.15 | = 1.15.0 | no fix published | NVD |
| 1.16 | = 1.16.0 | no fix published | NVD |
| 1.17 | = 1.17.0 | no fix published | NVD |
| 1.18 | = 1.18.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 245.x | = 245 | no fix published | NVD |
| 246.x | = 246 | no fix published | NVD |
| 247.x | = 247 | no fix published | NVD |
| 248.x | = 248 | no fix published | NVD |
| 249.x | = 249 | no fix published | NVD |
| 250.x | = 250 | no fix published | NVD |
| 251.x | = 251 | no fix published | NVD |
| 252.x | = 252 | no fix published | NVD |
| 253.x | = 253 | no fix published | NVD |
| 254.x | = 254 | no fix published | NVD |
| 255.x | = 255 | no fix published | NVD |
| 256.x | = 256 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.cloudfoundry.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.07.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-200read 2026-10-23
- FIRST EPSSEPSS score1.4 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2017-08-21
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-8037?
Is CVE-2017-8037 actively exploited?
What is the CVSS score for CVE-2017-8037?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.