Approved changes feed: RSS · Atom
cpe:2.3:a:cloud_foundry:diego:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Cloud Foundry (bbc462c7-a964-5178-97e1-18033ab4dbd3) |
|---|---|
| Product | Diego (e384e44f-cf9c-5e5a-a4f8-b50da90fcb2f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/cloudfoundry/diego-release |
purl2cpe | 2026-06-01 10:14:44.585660 |
pkg:golang/github.com/cloudfoundry/diego-release |
purl2cpe | 2026-06-01 10:14:44.585664 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-1265 |
vulnerable | 2026-06-03 14:38:30.719170 |
Details available
Cloud Foundry Diego, release versions prior to 2.8.0, does not properly sanitize file paths in tar and zip files headers. A remote attacker with CF admin privileges can upload a malicious buildpack that will allow a complete takeover of a Diego Cell VM and access to all apps running on that Diego Cell.
Published: 2018-06-06T20:00:00.000Z
Updated: 2024-09-17T02:21:31.743Z Reference links |
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.