CVE-2018-1265

N/A

Published: June 6, 2018 at 08:00 PM UTC

Updated: June 17, 2026 at 01:50 AM UTC

3 products affected across 2 vendorsCF DeploymentCloud Foundry DiegoDiego

Using Diego by Cloud Foundry?

Get instant alerts when new vulnerabilities affect Diego - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

CF Deployment · Cloudfoundry

95%

v < 1.37.0

Affected range stops below 1.37.0, so it looks safe — our inference, not a vendor statement

Cloud Foundry Diego · Pivotal

95%

v < 2.8.0

Affected range stops below 2.8.0, so it looks safe — our inference, not a vendor statement

Diego · Cloudfoundry

60%

v < 2.8.0

Affected range stops below 2.8.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

x_refsource_CONFIRMThird Party Advisory

Source: [email protected]

https://www.cloudfoundry.org/blog/cve-2018-1265/

CVSS

6.5MEDIUM[email protected]

Confidentiality: PARTIAL
Integrity: PARTIAL
Availability: PARTIAL

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-434

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card