dbcve.org
Garden LinuxApplication · Cloudfoundry

CVE-2016-0761

CRITICAL · 9.8 CVSS v3.1 Published 2017-05-25
Fix available
A fix is available. Upgrade to after 0.332.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Cloud Foundry Garden-Linux versions prior to v0.333.0 and Elastic Runtime 1.6.x version prior to 1.6.17 contain a flaw in managing container files during Docker image preparation that could be used to delete, corrupt or overwrite host files and directories, including other container filesystems on the host.

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 confidence

This is a critical container escape vulnerability in Cloud Foundry's Garden-Linux container management and Elastic Runtime. The flaw exists in how container files are managed during Docker image preparation, allowing improper file handling that can delete, corrupt, or overwrite host files and directories, including other container filesystems. This breaks container isolation and allows privilege escalation from within a container to the host.

MitigationUpgrade Garden-Linux to v0.333.0 or later, and Elastic Runtime to 1.6.17 or later. These patches fix the file handling logic to prevent path traversal and unauthorized host file manipulation during container operations.

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
Garden LinuxApplication
Affected:<= 0.332.0
Cloud Foundry Elastic RuntimeApplication
Affected:= 1.6.0= 1.6.1= 1.6.2= 1.6.3= 1.6.4= 1.6.5= 1.6.6= 1.6.7= 1.6.8= 1.6.9= 1.6.10= 1.6.11

CVSS 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Garden-Linux version
    Run 'garden-linux --version' or check the package manager for the installed garden-linux package version (e.g., dpkg -l garden-linux or rpm -qi garden-linux)
    Affected if The installed version is 0.332.0 or lower
  2. Identify Cloud Foundry Elastic Runtime version
    Check the Cloud Foundry release manifest or BOSH deployment configuration for the cf-release or elastic-runtime version number
    Affected if The Elastic Runtime version is between 1.6.0 and 1.6.11 inclusive
  3. Confirm Garden container management is active
    Inspect running Garden-Linux container processes (ps aux | grep garden) and verify the Garden daemon is operational on the host
    Affected if Garden-Linux is actively managing containers and the version is <= 0.332.0 or Elastic Runtime is 1.6.0-1.6.11
  4. Verify Docker image operations are performed
    Check container creation logs or audit records for Docker image layer operations (garden pull, docker pull, or image import operations)
    Affected if Docker image preparation or layer operations are performed using a vulnerable Garden-Linux version

You are affected if Garden-Linux version is 0.332.0 or lower, or if Cloud Foundry Elastic Runtime version is any version from 1.6.0 through 1.6.11, and container operations are being performed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.332.0
Interim mitigation

Upgrade Garden-Linux to v0.333.0 or later, and Elastic Runtime to 1.6.17 or later. These patches fix the file handling logic to prevent path traversal and unauthorized host file manipulation during container operations.

Recommended fix High confidence

Garden Linux >= 0.333.0 | Cloud Foundry Elastic Runtime >= 1.6.17

  1. 1. Identify the Garden-Linux version currently deployed in your Cloud Foundry environment
  2. 2. For Garden-Linux: Upgrade to version 0.333.0 or later
  3. 3. For Cloud Foundry Elastic Runtime: Upgrade to version 1.6.17 or later
  4. 4. Verify the upgrade was successful by checking the Garden-Linux and Elastic Runtime versions post-deployment
  5. 5. Test container creation and Docker image preparation functionality to ensure the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Garden Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-0761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-0761 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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