Snyk team has found four vulnerabilities collectively called “Leaky Vessels” that impact the runc and Buildkit container infrastructure and build tools, potentially allowing attackers to perform container escape on various software products.
On January 31, 2024, Buildkit fixed the flaws with version 0.12.5, and runc addressed the security issue impacting it on version 1.1.12.
Docker released version 4.27.0 on the same day, incorporating the secured versions of the components in its Moby engine, with versions 25.0.1 and 24.0.8.
Note that this news are important, I only want to give some peace of mind to the many amateurs self-hosting out there ;) Don’t panic. Think about how such attacker might gain access. There’s always a practical difference between a vulnerability being there and how easily it is exploitable. Most CVEs are theoretical, and combining 4 of them would be even more difficult. From what I read, the vulnerability would be in the Dockerfile itself. Also, you need to weigh in the motivation such attacker would have. If you’re an average netizen is different from a multi billion dollar company website. So, the attacker would need to meet all those conditions described in the CVEs and even in that case, they might escape the container only to find it was installed in rootless mode, so they just have access as regular user. But that’s depending on how docker was installed.
If you are relying on Docker as a security boundary you are making a mistake.
Docker isolation is good enough to keep honest people honest but isn’t good enough to keep out malicious actors. The Linux kernel API is simply too large of an attack surface to be highly secure.
If you want to run completely untrusted software you want a VM boundary at a very minimum. Ideally run it on completely separate hardware. There are few exceptions like browser isolation and gVisor which are strong software isolation without a VM but docker or any Linux container runner is not on that list. If the software has direct access to the host kernel it shouldn’t be considered secure.
Don’t run docker, so far it has proven quite insecure, and that was by design at first because docker was created for development environments and not for deployment.
Later docker added better security, because they understood the value in deployment too. But many distro are still insecure by default and it takes both the effort of sysadmins and image developers to deploy securely docker containers.
I switched to Podman: no daemon, no socket, no root operations out of the box. And the transition is basically seamless too.
I believe podman and containerd use
runcunder the hood so they’re also affected by this container escape vulnerability. You should update it to the latest version.
Honestly, if you’re running public facing services, you should run the latest everything you can. There’s a risk that stuff breaks, but at least you’re not having to worry about patched exploits.
I would add latest, security wise, not everything. That would be a recipe for disaster imo.
again and again … docker is becoming a joke
Every software has security vulnerabilities. The important thing is just that they get fixed quickly when they’re found and it seems like that was the case here.
I use <insert obscure software> instead, it has no vulnerabilities!
It has no known vulnerabilities.
I like to describe this as a game of peekaboo.
Where’s the vulnerability?
There it is!
Where’s the vulnerability?
(Not opening eyes) Huh, I guess there are none!
