How I Hacked Play-with-Docker and Remotely Ran Code on the Host

guest · Jan 14, 2019

How I Hacked Play-with-Docker and Remotely Ran Code on the Host
January 14, 2019
https://www.cyberark.com/threat-res...ith-docker-and-remotely-ran-code-on-the-host/

Play-with-Docker (PWD), Docker’s playground website, allows beginners to run Docker commands in a matter of seconds. Built on a number of hosts with each running multiple student’s containers, it’s a great place to learn Docker.
[...] all containers share the same kernel code. This is what makes containers so lightweight and easy to manipulate, but it is also a weak link in the Linux containers chain.
[...]
Conclusion
Gaining host access from a Linux container should be a very difficult task, if not impossible. In this PWD example, that’s not the case.

The reason is quite simple: PWD uses a privileged container and, prior to the fix, failed to secure it properly.
This makes an escape from the PWD container to the host difficult – but not impossible as we’ve shown in this post.
Click to expand...

Disclosure Timeline

November 6, 2018: Container escape reported to PWD maintainers

November 7, 2018: PWD maintainers responded that a fix will be implemented shortly

January 7, 2019: CyberArk confirmed that the vulnerability was fixed

Click to expand...

mirimir · Jan 15, 2019

OK, so I don't know that much about Docker. But I do know that it's not safe to provide shell access to containers.

Log in or Sign up

How I Hacked Play-with-Docker and Remotely Ran Code on the Host

guest Guest

mirimir Registered Member

Log in or Sign up

How I Hacked Play-with-Docker and Remotely Ran Code on the Host

guest Guest

mirimir Registered Member

Useful Searches