this post was submitted on 02 Feb 2024
28 points (100.0% liked)

Cybersecurity

5687 readers
18 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago
MODERATORS
 

Seems like a really serious vulnerability, any container attack or malicious image could take over a container host if there's no hardening on the containers.

all 5 comments
sorted by: hot top controversial new old
[–] mumblerfish@lemmy.world 4 points 9 months ago (2 children)

What are runc, buildkit, moby and docker desktop? Are these tools part of a normal docker setup on linux?

[–] jlh@lemmy.jlh.name 4 points 9 months ago

Yes, the runc vulnerability affects both docker cli and podman cli.

Docker and Kubernetes use containerd, and Podman uses runc directly.

https://github.com/containerd/containerd/pull/9724

https://github.com/containers/podman/pull/21483

Do not run any untrusted images until the vulnerability is fixed, especially not as root.

[–] honey_mesquite@sh.itjust.works 3 points 9 months ago* (last edited 9 months ago)

Docker Desktop won't really affect you as a Linux user, but moby/buildkit serves as the basis for "docker build" when building docker images. Runc is one of the base packages used for the software and so this will affect nearly all users of Docker until it gets resolved.