Compromised Host if Docker Task Runner is used

[Cloudnaut]

Hi,

I am figuring out how I can harden the underlying docker security for my bamboo agents. Using the the Docker Task Configuration the "Additional arguments" Input field caught my attention. This field allows you to run the container in --privileged mode which is fatal if some one puts sth like the following into the command field

dd if=/dev/zero of=/dev/sda bs=512 count=1 conv=notrunc

(Please see the attached pic for the configuration)

This compromises and destroys the bamboo host machine. Using gVisor or namespaces to harden the security is not possible due to the use of --net=host option in the docker runner.

Happy to hear more about your security setup for the bamboo agent hosts

[Alexey Chystoprudov]

If users have access to plan configuration they can use same script task to do the thing. That's why it's important to separate Bamboo Server and Bamboo agents. Agents should be executed at some environment which you're not afraid to break if you don't trust users.