Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

app containers can break weave and inject code by overwriting /w/w #1201

Closed
rade opened this issue Jul 20, 2015 · 2 comments
Closed

app containers can break weave and inject code by overwriting /w/w #1201

rade opened this issue Jul 20, 2015 · 2 comments

Comments

@rade
Copy link
Member

rade commented Jul 20, 2015

$ weave launch
$ eval $(weave env)
$ docker run --rm -ti ubuntu
root@65a8d6e07d6b:/# rm /w/w
root@65a8d6e07d6b:/# exit
exit
$ docker run --rm -ti ubuntu
exec: "/w/w": stat /w/w: no such file or directory
Error response from daemon: 87a39af540d39d0bf6bfc9e9b9facb22aba5f2ab2aea2efbe08ed8c9bff8c5fd container is not running.

And instead of removing /w/w I could also inject arbitrary code that will execute next time any container executes /w/w.

Solution: mount the volume read-only with -v ...:ro.

@joserivca
Copy link

Hi rade,
Weave inyect all my containers with "/w/w",
i cant execute any container
how can roll back in all my containers??

@rade
Copy link
Member Author

rade commented Sep 23, 2016

@joserivca that is not what this issue is about. Please open a new one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants