CVE-2017-8048
No exploitation reported by the sources we read.
- Published2017-10-04
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 capi-release versions 1.33.0 and later, prior to 1.42.0 and cf-release versions 268 and later, prior to 274, the original fix for CVE-2017-8033 introduces an API regression that allows a space developer to execute arbitrary code on the Cloud Controller VM by pushing a specially crafted application. NOTE: 274 resolves the vulnerability but has a serious bug that is fixed in 275.
Timeline
dates in UTC- 2017-10-0401:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-8048?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-8048?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.33 | = 1.33.0 | no fix published | NVD |
| 1.34 | = 1.34.0 | no fix published | NVD |
| 1.35 | = 1.35.0 | no fix published | NVD |
| 1.36 | = 1.36.0 | no fix published | NVD |
| 1.37 | = 1.37.0 | no fix published | NVD |
| 1.38 | = 1.38.0 | no fix published | NVD |
| 1.39 | = 1.39.0 | no fix published | NVD |
| 1.40 | = 1.40.0 | no fix published | NVD |
| 1.41 | = 1.41.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 268.x | = 268 | no fix published | NVD |
| 269.x | = 269 | no fix published | NVD |
| 270.x | = 270 | no fix published | NVD |
| 271.x | = 271 | no fix published | NVD |
| 272.x | = 272 | no fix published | NVD |
| 273.x | = 273 | 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.8read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- FIRST EPSSEPSS score1.2 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2017-10-04
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-8048?
Is CVE-2017-8048 actively exploited?
What is the CVSS score for CVE-2017-8048?
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.