CVE-2015-5350
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Garden versions 0.22.0-0.329.0, a vulnerability has been discovered in the garden-linux nstar executable that allows access to files on the host system. By staging an application on Cloud Foundry using Diego and Garden installations with a malicious custom buildpack an end user could read files on the host system that the BOSH-created vcap user has permissions to read and then package them into their app droplet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe nstar executable in Garden containers versions 0.22.0-0.329.0 contains a file traversal vulnerability allowing containerized applications to escape isolation and read files on the host system that the vcap user has permissions to access. Attackers exploit this by staging a malicious buildpack on Cloud Foundry deployments using Diego and vulnerable Garden versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.330.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Garden container runtime installationLocate the Garden (garden-linux or garden-runc) installation in your Cloud Foundry environment. Check for the garden-* package or binary on Diego cells (or equivalent compute nodes).Affected if Garden is installed and part of your Cloud Foundry deployment.
-
Determine the installed Garden versionRun 'garden --version' or check the package/version manifest for the garden component in your Cloud Foundry deployment. Compare the version number against the 0.22.0 to 0.329.0 range.Affected if The installed Garden version falls within 0.22.0 through 0.329.0 inclusive.
-
Confirm Cloud Foundry uses Diego backendCheck your Cloud Foundry deployment configuration to verify whether the Diego backend is enabled. Diego is required for the nstar vulnerability to be exploitable in this context.Affected if Your Cloud Foundry deployment uses Diego as the container runtime backend.
-
Verify buildpack staging is enabledConfirm that buildpack-based application staging is enabled in your Cloud Foundry environment. The nstar executable is used during the staging phase to transfer buildpack artifacts.Affected if Buildpack staging functionality is available and being used.
You are affected if your Garden version is below 0.330.0 AND you are running Cloud Foundry with the Diego backend where application staging with buildpacks is performed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.330.0
Upgrade Garden to version 0.330.0 or later to patch the nstar vulnerability. Alternatively, ensure untrusted buildpacks are not allowed in Cloud Foundry deployments using affected Garden versions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5350 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data