News for hackers. Stuff that matters.
Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by pelagicAustral on Tuesday March 26, 2024 @11:11AM (#39828916)
Awwww Fuck me! that's my lazy afternoon gone now
Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by eikenberry on Tuesday March 26, 2024 @12:23PM (#39829660)
Fixed kernel was released to Debian stable well over a month ago (my logs have it installed on 2/12). So unless you ignore kernel security updates you should already be covered.
Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by blincoln on Tuesday March 26, 2024 @11:46PM (#39835525)
Unfortunately, this was almost the same time that the Debian devs also pushed the ill-conceived Nvidia-driver-breaking kernel patch, so I wouldn't be surprised if a lot of people had disabled kernel updates.
Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by richardwhiuk on Tuesday March 26, 2024 @11:24AM (#39829089)
This is local privilege escalation only right?
Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by Unroll0201 on Tuesday March 26, 2024 @11:31AM (#39829154)
Correct, but it is definitively worth updating for on high-profile systems.

I have not tested it, but because I have included the namespace escape in the exploit for KernelCTF, it may be able to break out of LXC containers and privileged Docker containers running on vulnerable Linux kernels.

Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by dathinab on Tuesday March 26, 2024 @12:25PM (#39829691)
if it works for LXC containers shouldn't it also work for unprivileged (but non VM) docker containers?
Re:Debian/Ubuntu privilege escalation PoC exploit for CVE-20... by Unroll0201 on Tuesday March 26, 2024 @02:00PM (#39830843)
This is an educated guess, but I believe unprivileged Docker containers cannot create (user) namespaces. Hence, the vulnerability cannot be triggered, since the exploit requires interaction with nf_tables, which requires (namespace) root.

LXC containers and privileged Docker containers allow these namespaces to be made inside of them, whilst unprivileged Docker containers do not.