This is probably known and unavoidable, but it may be worth documenting as unsafe: --enable=docker lets an agent bypass the sandbox’s filesystem restrictions. Because Docker can access the host filesystem, an agent could run an existing local image, mount the user’s home directory, and extract/overwrite files from it.
A very simple reproduction:
safehouse --enable=docker docker run --volume=$HOME/.zshrc:/flag --rm -it alpine:3.22 cat flag
Prints your .zshrc. Assumes alpine:3.22 is already pulled locally.
This is probably known and unavoidable, but it may be worth documenting as unsafe:
--enable=dockerlets an agent bypass the sandbox’s filesystem restrictions. Because Docker can access the host filesystem, an agent could run an existing local image, mount the user’s home directory, and extract/overwrite files from it.A very simple reproduction:
Prints your .zshrc. Assumes
alpine:3.22is already pulled locally.