3 ms·

There are a lot more problems than you think with letting users have arbitrary code execution. And no, Docker is not an acceptable security solution for this, s

by zx2c4 11y ago

There are a lot more problems than you think with letting users have arbitrary code execution. And no, Docker is not an acceptable security solution for this, since it's most certainly possible to break out of containers. Even if you're using a dedicated VM, this is not a good idea. And from a brief look at glot-code-runner, it doesn't seem like there's even that much built in to protect against various forms of use. A more sane design would be to use something like emscripten to enable all these different languages to run in the browser.

Lambent_Cactus 11y ago
We built something like this for our our data science platform (https://civisanalytics.com/products/end-to-end-data-science/ https://civisanalytics.com/products/end-to-end-data-science/), but the containers run on a group of workers that are isolated in one VPC per customer. And even that is for enterprise customers where you have some layer of accountability - I can't imagine opening it up to the wild internet.
dhaivatpandya 11y ago
"Docker is not an acceptable security solution for this, since it's most certainly possible to break out of containers." Could you point to some resources that show that it is possible to break out of Docker containers? I understand that there have been bugs in the past that have caused this (using that to conclude that glot.io shouldn't use Docker is a bit like saying OpenSSL is now useless because of heartbleed) but it seems unlikely that breaking out of containers is possible due to the way Docker is designed.
- seanp2k2 11y ago
  http://www.cvedetails.com/product/28125/Docker-Docker.html?vendor_id=13534 http://www.cvedetails.com/product/28125/Docker-Docker.html?v... https://github.com/docker/docker/issues/12317 https://github.com/docker/docker/issues/12317 https://github.com/gabrtv/shocker https://github.com/gabrtv/shocker https://www.oreilly.com/ideas/docker-security https://www.oreilly.com/ideas/docker-security I'm sure there will be more Edit: yup, as cited below: https://conference.hitb.org/hitbsecconf2016ams/sessions/escape-from-the-docker-kvm-qemu-machine/ https://conference.hitb.org/hitbsecconf2016ams/sessions/esca...
  - cyphar 11y ago
    Most of the vulnerabilities you mention are actually kernel vulnerabilities. While they affect Docker, they more accurately affect everything that uses "Linux containers". Although, Docker did have a bad history of security bugs with symlinks. But given the fact that Linux doesn't have real containers, I feel very conflicted about opening that up to the internet.
- vellum 11y ago
  https://www.nccgroup.trust/globalassets/our-research/us/whitepapers/2016/april/ncc_group_understanding_hardening_linux_containers-10pdf/ https://www.nccgroup.trust/globalassets/our-research/us/whit...

by zx2c4 11y ago

Lambent_Cactus 11y ago

We built something like this for our our data science platform (https://civisanalytics.com/products/end-to-end-data-science/ https://civisanalytics.com/products/end-to-end-data-science/), but the containers run on a group of workers that are isolated in one VPC per customer. And even that is for enterprise customers where you have some layer of accountability - I can't imagine opening it up to the wild internet.

dhaivatpandya 11y ago

"Docker is not an acceptable security solution for this, since it's most certainly possible to break out of containers." Could you point to some resources that show that it is possible to break out of Docker containers? I understand that there have been bugs in the past that have caused this (using that to conclude that glot.io shouldn't use Docker is a bit like saying OpenSSL is now useless because of heartbleed) but it seems unlikely that breaking out of containers is possible due to the way Docker is designed.

seanp2k2 11y ago
http://www.cvedetails.com/product/28125/Docker-Docker.html?vendor_id=13534 http://www.cvedetails.com/product/28125/Docker-Docker.html?v... https://github.com/docker/docker/issues/12317 https://github.com/docker/docker/issues/12317 https://github.com/gabrtv/shocker https://github.com/gabrtv/shocker https://www.oreilly.com/ideas/docker-security https://www.oreilly.com/ideas/docker-security I'm sure there will be more Edit: yup, as cited below: https://conference.hitb.org/hitbsecconf2016ams/sessions/escape-from-the-docker-kvm-qemu-machine/ https://conference.hitb.org/hitbsecconf2016ams/sessions/esca...
- cyphar 11y ago
  Most of the vulnerabilities you mention are actually kernel vulnerabilities. While they affect Docker, they more accurately affect everything that uses "Linux containers". Although, Docker did have a bad history of security bugs with symlinks. But given the fact that Linux doesn't have real containers, I feel very conflicted about opening that up to the internet.
vellum 11y ago
https://www.nccgroup.trust/globalassets/our-research/us/whitepapers/2016/april/ncc_group_understanding_hardening_linux_containers-10pdf/ https://www.nccgroup.trust/globalassets/our-research/us/whit...