Leaky Vessels flaws allow hackers to escape Docker, runc containers
www.bleepingcomputer.com
Four vulnerabilities collectively called "Leaky Vessels" allow hackers to escape containers and access data on the underlying host operating system.

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.

  • Shimitar@feddit.itEnglish
    0·
    9 months ago

    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.

    • redcalcium@lemmy.instituteOPEnglish
      1·
      9 months ago

      I believe podman and containerd use runc under the hood so they’re also affected by this container escape vulnerability. You should update it to the latest version.