You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tl;dr is that since there is no locking here, an unprivileged process can create two threads. One will do a call to create a file, and another will remove the file immediately after it is created by the create_file_fs call, then symlink it to another file - owned by root - and then the kopen will just happily open the symlink. At this point, the unprivileged process can open any file owned by root.
I can share a proof of concept of exploiting that vulnerability if you want.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
There is a race condition in the
sys_open
syscall with theO_CREAT
flag which allows for privilege escalation.toaruos/kernel/sys/syscall.c
Lines 400 to 402 in 28190ad
The tl;dr is that since there is no locking here, an unprivileged process can create two threads. One will do a call to create a file, and another will remove the file immediately after it is created by the
create_file_fs
call, then symlink it to another file - owned by root - and then thekopen
will just happily open the symlink. At this point, the unprivileged process can open any file owned by root.I can share a proof of concept of exploiting that vulnerability if you want.
This bug was found during HXP 38C3 CTF competition (which contained a challenge with TaoruOS).
The text was updated successfully, but these errors were encountered: