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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
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.
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.
Oh. I didn’t meant to incite breaking any of the golden rules of cyber safety: (1) always update, (2) never host WordPress ;)