BlanK0 to Security · 10 months agoLeaky Vessels flaws allow hackers to escape Docker, runc containerswww.bleepingcomputer.comexternal-linkmessage-square5fedilinkarrow-up111arrow-down10cross-posted to: securitynews@infosec.publinuxselfhosted@lemmy.world
arrow-up111arrow-down1external-linkLeaky Vessels flaws allow hackers to escape Docker, runc containerswww.bleepingcomputer.comBlanK0 to Security · 10 months agomessage-square5fedilinkcross-posted to: securitynews@infosec.publinuxselfhosted@lemmy.world
minus-squareBlanK0OPlinkfedilinkarrow-up1·10 months agoMaybe 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 🤔
minus-squareOisteink@feddit.nllinkfedilinkarrow-up2arrow-down1·10 months agoPossibly - so if I keep staying clear of fishy apps I’d be fine. Does this affect lxc/d as welll?
minus-squareBlanK0OPlinkfedilinkarrow-up2·10 months agoIt 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
minus-squareMaienM@sopuli.xyzlinkfedilinkarrow-up4·10 months agoKubernetes and docker both use containerd, which in turn uses runc which is what the vulnerability is in.
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.