News for hackers. Stuff that matters.
Re:CVE-2026-31431: Copy Fail vs. rootless containers by grimblee on Tuesday May 05, 2026 @11:33AM (#48023949)
If I understand correctly, rootfull podman with --userns=auto would also prevent the privilege escalation ?
Re:CVE-2026-31431: Copy Fail vs. rootless containers by cpach on Tuesday May 05, 2026 @11:34AM (#48023970)
How?
Re:CVE-2026-31431: Copy Fail vs. rootless containers by grimblee on Tuesday May 05, 2026 @04:20PM (#48027949)
--userns=auto asign a different namespace for each container, so if you escape it you get a random uid far far away from root it also protects other containers from the compromise since they each have their own namespace and uid/gid range, the drawback though is that you can't mount shared volume unless you use a pod, since you would see files from outside your uid/gid range as owned by nobody and inaccessible.
Re:CVE-2026-31431: Copy Fail vs. rootless containers by cpach on Tuesday May 05, 2026 @04:32PM (#48028100)
That might make Copy Fail harder to exploit, but I still wouldn’t bet money on CF being impossible to use in that scenario.
Re:CVE-2026-31431: Copy Fail vs. rootless containers by grimblee on Tuesday May 05, 2026 @05:50PM (#48029112)
Since in --userns=auto, root inside the container gets assigned to the first uid of the uid range assigned by podman, copyfail would succeed but you'd get uid 647831 and be able to do nothing with it
Re:CVE-2026-31431: Copy Fail vs. rootless containers by angry_octet on Tuesday May 05, 2026 @07:49PM (#48030349)
No it wouldn't. The exploit is not impacted by namespaces.