Selfhosted

61103 readers

277 users here now

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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

159

PSA: Update your docker installation. Leaky Vessels flaws allow hackers to escape Docker, runc containers (www.bleepingcomputer.com)

submitted 2 years ago by redcalcium@lemmy.institute to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] anzo@programming.dev 3 points 2 years ago (1 children)

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.pub 2 points 2 years ago* (last edited 2 years ago) (1 children)

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.

[–] anzo@programming.dev 2 points 2 years ago

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