CVE-2017-8037
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ if you've already worked around this in production โ publish your fix to the community-verified tier.
โ Propose a mitigation on Community โ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| cloudfoundry | capi-release | 1.7.0 | |
| cloudfoundry | capi-release | 1.8.0 | |
| cloudfoundry | capi-release | 1.9.0 | |
| cloudfoundry | capi-release | 1.10.0 | |
| cloudfoundry | capi-release | 1.11.0 | |
| cloudfoundry | capi-release | 1.12.0 | |
| cloudfoundry | capi-release | 1.13.0 | |
| cloudfoundry | capi-release | 1.14.0 | |
| cloudfoundry | capi-release | 1.15.0 | |
| cloudfoundry | capi-release | 1.16.0 | |
| cloudfoundry | capi-release | 1.17.0 | |
| cloudfoundry | capi-release | 1.18.0 | |
| cloudfoundry | capi-release | 1.19.0 | |
| cloudfoundry | capi-release | 1.20.0 | |
| cloudfoundry | capi-release | 1.21.0 | |
| cloudfoundry | capi-release | 1.22.0 | |
| cloudfoundry | capi-release | 1.23.0 | |
| cloudfoundry | capi-release | 1.24.0 | |
| cloudfoundry | capi-release | 1.25.0 | |
| cloudfoundry | capi-release | 1.26.0 | |
| cloudfoundry | capi-release | 1.27.0 | |
| cloudfoundry | capi-release | 1.28.0 | |
| cloudfoundry | capi-release | 1.29.0 | |
| cloudfoundry | capi-release | 1.30.0 | |
| cloudfoundry | capi-release | 1.31.0 | |
| cloudfoundry | capi-release | 1.32.0 | |
| cloudfoundry | capi-release | 1.33.0 | |
| cloudfoundry | capi-release | 1.34.0 | |
| cloudfoundry | capi-release | 1.35.0 | |
| cloudfoundry | capi-release | 1.36.0 | |
| cloudfoundry | capi-release | 1.37.0 | |
| cloudfoundry | cf-release | 245 | |
| cloudfoundry | cf-release | 246 | |
| cloudfoundry | cf-release | 247 | |
| cloudfoundry | cf-release | 248 | |
| cloudfoundry | cf-release | 249 | |
| cloudfoundry | cf-release | 250 | |
| cloudfoundry | cf-release | 251 | |
| cloudfoundry | cf-release | 252 | |
| cloudfoundry | cf-release | 253 | |
| cloudfoundry | cf-release | 254 | |
| cloudfoundry | cf-release | 255 | |
| cloudfoundry | cf-release | 256 | |
| cloudfoundry | cf-release | 257 | |
| cloudfoundry | cf-release | 258 | |
| cloudfoundry | cf-release | 259 | |
| cloudfoundry | cf-release | 260 | |
| cloudfoundry | cf-release | 261 | |
| cloudfoundry | cf-release | 262 | |
| cloudfoundry | cf-release | 263 | |
| cloudfoundry | cf-release | 264 | |
| cloudfoundry | cf-release | 265 | |
| cloudfoundry | cf-release | 266 | |
| cloudfoundry | cf-release | 267 | |
| cloudfoundry | cf-release | 268 | |
| cloudfoundry | cf-release | 269 | |
References
CWEs
CWE-200
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.