security fix to runc in docker-1.12.3 wasn't picked
Bug #1675288 reported by
Yubao Liu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
runc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
https:/
The steps are very clear, it's very easy to recur, so I don't repeat here.
The CVE link: https:/
[Test case]
$ tmp=$(mktemp -d)
$ cd $tmp
$ cat > Dockerfile << EOF
FROM debian
RUN useradd example
RUN id
USER example
RUN id
RUN cat /etc/shadow
CMD /bin/bash
EOF
$ docker build --no-cache -t example .
The 'cat /etc/shadow' in the Dockerfile should fail.
[Regression potential]
We're fixing this by moving to the exact commit of runc the docker 1.12.6 release expects, so there shouldn't be any issues. In addition https:/
CVE References
information type: | Private Security → Public |
description: | updated |
Changed in runc (Ubuntu Yakkety): | |
status: | Fix Committed → Won't Fix |
To post a comment you must log in.
This bug was fixed in the package runc - 1.0.0~rc2+ docker1. 12.6-0ubuntu1
--------------- rc2+docker1. 12.6-0ubuntu1) zesty; urgency=medium
runc (1.0.0~
* Update to the precise commit included in Docker 1.12.6 (LP: #1675288)
-- Tianon Gravi <email address hidden> Fri, 24 Mar 2017 14:26:40 -0700