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.

  • sj_zero@lotide.fbxl.net
    412·
    10 months ago

    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.

  • adr1an@programming.devEnglish
    3·
    10 months ago

    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.

    • xinayder@infosec.pubEnglish
      2·
      9 months ago

      It’s still not an excuse to just ignore the security update because you might not be a target for hackers.

      Just check your logs, there’s probably a dozen or more requests trying to access wordpress pages on your server, or login via SSH. They want to take over your server so it can be part of a botnet.

      • adr1an@programming.devEnglish
        2·
        9 months ago

        Oh. I didn’t meant to incite breaking any of the golden rules of cyber safety: (1) always update, (2) never host WordPress ;)

  • Shimitar@feddit.itEnglish
    31·
    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.