# CVE-2017-14388: Other in GrootFS release GrootFS release 0.3.x versions prior to 0.30.0

> Attackers can poison the GrootFS volume cache with crafted images, potentially leading to unauthorized code execution or data modification in Cloud Foundry environments.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Nov 2017
- **Updated:** 5 Aug 2024

## What is CVE-2017-14388?

CVE-2017-14388 is a high-severity vulnerability in GrootFS release GrootFS release 0.3.x versions prior to 0.30.0, published on 13 Nov 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cloud Foundry Foundation GrootFS release 0.3.x versions prior to 0.30.0 do not validate DiffIDs, allowing specially crafted images to poison the grootfs volume cache. For example, this could allow an attacker to provide an image layer that GrootFS would consider to be the Ubuntu base layer.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-14388?

It affects 1 product.


Products: Pivotal Software Grootfs.

## How do I fix CVE-2017-14388?

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

## Is CVE-2017-14388 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14388 and fix it if it is affected.

What it is: CVE-2017-14388 is a high-severity vulnerability in GrootFS release GrootFS release 0.3.x versions prior to 0.30.0, published on 13 Nov 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-14388 in the wild and no public exploit code.

Affected product: GrootFS release GrootFS release 0.3.x versions prior to 0.30.0. 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-2017-14388/ (Markdown: https://insights.sbomify.com/CVE-2017-14388/index.md)
```

## Sources

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

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