Bsecurity·SecuritybyBlanK0 Leaky Vessels flaws allow hackers to escape Docker, runc containershttps://www.bleepingcomputer.com/news/security/leaky-vessels-flaws-allow-hackers-to-escape-docker-runc-containers/Open linkView original on lemmy.ml9Comments5Reply
OOisteink feddit.nl4Hide 4 repliesWhat are the hackers doing in my container in the first place? And how did they drop to shell?1Reply
BBlanK0 replylemmy.ml3Hide 3 repliesMaybe if you try to run fishy apps on containers then the hacker can exploit out of the container. I guess that's a possible scenario 🤔1Reply
OOisteink replyfeddit.nl2Hide 2 repliesPossibly - so if I keep staying clear of fishy apps I’d be fine. Does this affect lxc/d as welll?1Reply
BBlanK0 replylemmy.ml1Hide 1 replyIt affects mainly docker and kubernets containers. I did a little research and apparently docker isn't based of lxc/lxd anymore, so I suppose that it doesn't affect those. Although I'm not sure what kubernets is based off2Reply
MMaienM replysopuli.xyzKubernetes and docker both use containerd, which in turn uses runc which is what the vulnerability is in.4Reply
5 replies
What are the hackers doing in my container in the first place? And how did they drop to shell?
Maybe if you try to run fishy apps on containers then the hacker can exploit out of the container. I guess that's a possible scenario 🤔
Possibly - so if I keep staying clear of fishy apps I’d be fine.
Does this affect lxc/d as welll?
It affects mainly docker and kubernets containers. I did a little research and apparently docker isn't based of lxc/lxd anymore, so I suppose that it doesn't affect those. Although I'm not sure what kubernets is based off
Kubernetes and docker both use containerd, which in turn uses runc which is what the vulnerability is in.