Bug 1271253 (CVE-2014-8178) - CVE-2014-8178 docker: Attacker controlled layer IDs lead to local graph content poisoning
Summary: CVE-2014-8178 docker: Attacker controlled layer IDs lead to local graph conte...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: CVE-2014-8178
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1271259 1271260 1271261
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-13 13:38 UTC by Trevor Jay
Modified: 2019-09-29 13:38 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-13 14:01:37 UTC


Attachments (Terms of Use)

Description Trevor Jay 2015-10-13 13:38:13 UTC
Docker image layers are stored with a non-globally unique identifier vulnerable to a collision attack. These identifiers are shared during docker pull and push, allowing poisoning of a host's image cache. This allows maliciously crafted images to poison subsequently pulled images.

Independently discovered by Florian Weimer of Red Hat and Tõnis Tiigi of the Docker Engine Tem.

Comment 2 Trevor Jay 2015-10-13 13:48:47 UTC
Created docker-io tracking bugs for this issue:

Affects: fedora-all [bug 1271261]

Comment 3 Trevor Jay 2015-10-13 14:01:37 UTC
This issue is exploitable by malicious Docker images. Red Hat supports images from it's own registry, ISV images certified by the Red Hat certification program, and images using qualified customer content.

Marking this vulnerability and its children as "WONTFIX".

Comment 4 Daniel Walsh 2015-10-13 14:08:33 UTC
We will get the fix from docker when we release docker-1.9.

Comment 5 Vincent Danen 2015-10-15 17:22:52 UTC
Statement:

This issue is exploitable by malicious Docker images. Red Hat supports images from it's own registry, ISV images certified by the Red Hat certification program, and images using qualified customer content.

Comment 6 Trevor Jay 2016-10-17 03:08:28 UTC
Fixed in 1.8.3 and greater.


Note You need to log in before you can comment on or make changes to this bug.