News for hackers. Stuff that matters.
Re:Understanding Docker Container Escapes by tln on Saturday July 20, 2019 @05:05PM (#20488363)
Not sure about production workloads but its not just privileged containers you start that should be a concern.. anyone who can access /var/run/docker.sock can run a privileged container, so this can be a privilege escalation.

Because of this escape, giving access to /var/run/docker.sock to regular users is the same as giving them root access.

Also as the article says mounting /var/run/docker.sock is (now, because of this escape) the same as giving that container access to the host system.

Re:Understanding Docker Container Escapes by mclehman on Saturday July 20, 2019 @05:47PM (#20488585)
On the other side of things, my favorite demo for people new to docker who aren't yet aware that sudoless docker ~~ root access is:

    docker run -itv /:/host ubuntu chroot /host
Re:Understanding Docker Container Escapes by cyphar on Saturday July 20, 2019 @11:04PM (#20489736)
Or, even better use nsenter to join all the namespaces of PID 1 on the host (making your process an ordinary root process in the init namespaces).
Re:Understanding Docker Container Escapes by zapita on Saturday July 20, 2019 @06:23PM (#20488717)
Mounting /var/run/docker.sock has always been the same as full host access. That is a well-documented fact irrespective of this particular escape.