Selfhosted

61103 readers

605 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

[–] Shimitar@feddit.it 2 points 2 years ago (1 children)

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

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.

[–] Shimitar@feddit.it 1 points 2 years ago (1 children)

Podman can use different tools under the hood, will check which one I am using.

[–] redcalcium@lemmy.institute 1 points 2 years ago

I think on redhat/fedora it uses runc by default and on debian/arch it uses crun by default.