Cloudfoundry CAPI-release 1.14.0
Approved changes feed: RSS · Atom
cpe:2.3:a:cloudfoundry:capi-release:1.14.0:*:*:*:*:*:*:*
part: a version: 1.14.0 update: *
| Vendor | Cloudfoundry (3aa6768c-437d-5100-a420-b037598cadb4) |
|---|---|
| Product | Capi Release (80308457-c7a8-52d5-8d73-e9a1837c34af) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/cloudfoundry/capi-release |
purl2cpe | 2026-06-01 10:12:04.813592 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-8037 |
vulnerable | 2026-06-03 14:37:38.915313 |
Details available
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.
Published: 2017-08-21T22:00:00.000Z
Updated: 2024-08-05T16:19:29.884Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.