mirror of
https://github.com/RGBCube/serenity
synced 2025-07-26 06:37:35 +00:00
Kernel: Disallow executing SUID binaries if process is jailed
Check if the process we are currently running is in a jail, and if that is the case, fail early with the EPERM error code. Also, as Brian noted, we should also disallow attaching to a jail in case of already running within a setid executable, as this leaves the user with false thinking of being secure (because you can't exec new setid binaries), but the current program is still marked setid, which means that at the very least we gained permissions while we didn't expect it, so let's block it.
This commit is contained in:
parent
0e010790a4
commit
e598f22768
4 changed files with 23 additions and 2 deletions
|
@ -105,6 +105,7 @@ Special restrictions on filesystem also apply:
|
|||
- Write access is forbidden to kernel variables (which are located in `/sys/kernel/variables`).
|
||||
- Open access is forbidden to all device nodes except for `/dev/full`, `/dev/null`, `/dev/zero`, `/dev/random` and various
|
||||
other TTY/PTY devices (not including Kernel virtual consoles).
|
||||
- Executing SUID binaries is forbidden.
|
||||
|
||||
It was first added in the following [commit](https://github.com/SerenityOS/serenity/commit/5e062414c11df31ed595c363990005eef00fa263),
|
||||
for kernel support, and the following commits added basic userspace utilities:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue