# CVE-2014-8178: Other in CS Docker Engine

> Attackers can poison the Docker image cache by exploiting non-unique layer identifiers, potentially leading to compromised container images.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **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:** Yes
- **Published:** 4 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8178, GHSA-cx5m-7cfp-6prc, UBUNTU-CVE-2014-8178

## What is CVE-2014-8178?

CVE-2014-8178 is a medium-severity vulnerability in Opensuse Opensuse, published on 4 Dec 2019. 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

Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 do not use a globally unique identifier to store image layers, which makes it easier for attackers to poison the image cache via a crafted image in pull or push commands.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-8178?

It affects 3 products.


Products: Docker Cs Engine, Docker Docker, Opensuse Opensuse.

## How do I fix CVE-2014-8178?

Upgrade to a fixed version.

## Is CVE-2014-8178 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2014-8179](https://insights.sbomify.com/CVE-2014-8179/): Other in CS Docker Engine (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8178 and fix it if it is affected.

What it is: CVE-2014-8178 is a medium-severity vulnerability in Opensuse Opensuse, published on 4 Dec 2019. 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-2014-8178 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2014-8178/ (Markdown: https://insights.sbomify.com/CVE-2014-8178/index.md)
```

## Sources

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

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