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

> Attackers can bypass pull-by-digest validation in Docker Engine by injecting attributes into JSON manifests, compromising image integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8179, GHSA-7w47-v4xv-5crg, UBUNTU-CVE-2014-8179

## What is CVE-2014-8179?

CVE-2014-8179 is a high-severity vulnerability in Opensuse Opensuse, published on 4 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Docker Engine before 1.8.3 and CS Docker Engine before 1.6.2-CS7 does not properly validate and extract the manifest object from its JSON representation during a pull, which allows attackers to inject new attributes in a JSON object and bypass pull-by-digest validation.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 3 products.


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

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

Upgrade to a fixed version.

## Is CVE-2014-8179 being exploited?

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

## Other vulnerabilities in Opensuse Opensuse

- [CVE-2014-8178](https://insights.sbomify.com/CVE-2014-8178/): Other in CS Docker Engine (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8179 is a high-severity vulnerability in Opensuse Opensuse, published on 4 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-8179 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-8179/ (Markdown: https://insights.sbomify.com/CVE-2014-8179/index.md)
```

## Sources

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

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