News for hackers. Stuff that matters.
Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by fbdab103 on Sunday February 04, 2024 @12:48PM (#39252493)
Just this week there was a story[0] with a subthread about how Docker requires you to mount a volume, so it is better than launching shell scripts directly. I know all software has bugs, but Docker did not prioritize security and is unfit for isolation of untrusted code.

I will continue to stick with VMs as my security boundary.

[0] https://news.ycombinator.com/item?id=39240471

Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by hipadev23 on Sunday February 04, 2024 @01:03PM (#39252644)
Maybe I’m in the minority here, but I use containers for ease of packaging and deployment, security isn’t really my expectation for the container as I also rely on VMs for that aspect. I have a handful of long-running VMs with docker engine installed, and that serves as my application platform.
Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by flaminHotSpeedo on Sunday February 04, 2024 @01:09PM (#39252709)
Definitely not the minority, anyone who needs secure isolation for a container should be wrapping it in a single tenant VM
Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by throwoutway on Sunday February 04, 2024 @03:08PM (#39253872)
Firecracker has often been recommended (here on HN and elsewhere) for a VM-for container-execution model : https://github.com/firecracker-microvm/firecracker
Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by tptacek on Sunday February 04, 2024 @03:23PM (#39254032)
There's also Cloud Hypervisor, which is very similar, and based off some of the same crosvm code and ideas.

https://github.com/cloud-hypervisor/cloud-hypervisor

Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by westurner on Sunday February 04, 2024 @07:14PM (#39255908)
gvisor; `runsc`: https://gvisor.dev/docs/ :

> gVisor provides a virtualized environment in order to sandbox containers. The system interfaces normally implemented by the host kernel are moved into a distinct, per-sandbox application kernel in order to minimize the risk of a container escape exploit. gVisor does not introduce large fixed overheads however, and still retains a process-like model with respect to resource utilization.

https://news.ycombinator.com/item?id=38609105

kata containers: https://github.com/kata-containers :

> Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs.

Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by mrweasel on Sunday February 04, 2024 @12:52PM (#39252540)
Just pointing out the most VM / virtualization platforms have also had security problems where an attacker could escape the VM and access the underlying operating system.
Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by tptacek on Sunday February 04, 2024 @02:00PM (#39253220)
KVM vulnerabilities are rare compared to Linux kernel LPEs, which makes sense, because KVM is a relatively small part of the Linux kernel compared to the system call and driver attack surface. Containers are great, but shared-kernel security isolation of standard Unix programs doesn't work.
Re:Leaky Vessels flaws allow hackers to escape Docker, runc ... by flaminHotSpeedo on Sunday February 04, 2024 @01:18PM (#39252799)
The major difference is that VM's are intended to be a security boundary as a primary function, and give you tools like hardware virtualization or enforcing single tenancy for a given NUMA node to reduce the attack surface.