# CVE-2018-11084: Garden-runC prevents deletion of some app environments

> Authenticated attackers can cause denial of service for new app instances or scaling by exploiting file attribute handling in Cloud Foundry Garden-runC.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Sep 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hpg7-3mv4-7gc8

## What is CVE-2018-11084?

CVE-2018-11084 is a medium-severity denial of service vulnerability in Cloud Foundry Garden-runC, published on 18 Sep 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cloud Foundry Garden-runC release, versions prior to 1.16.1, prevents deletion of some app environments based on file attributes. A remote authenticated malicious user may create and delete apps with crafted file attributes to cause a denial of service for new app instances or scaling up of existing apps.

## Which versions are affected by CVE-2018-11084?

It affects 1 product.


Products: Cloudfoundry Garden-Runc.

## How do I fix CVE-2018-11084?

No fix has been published for CVE-2018-11084 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-11084 being exploited?

There is no known exploitation of CVE-2018-11084 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11084 and fix it if it is affected.

What it is: CVE-2018-11084 is a medium-severity denial of service vulnerability in Cloud Foundry Garden-runC, published on 18 Sep 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-11084 in the wild and no public exploit code.

Affected product: Cloud Foundry Garden-runC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-11084/ (Markdown: https://insights.sbomify.com/CVE-2018-11084/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-11084
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-11084
- OSV: https://osv.dev/vulnerability/CVE-2018-11084

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-11084/
Summaries are generated and may contain mistakes; the official description above is the record.