mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #477] Able to set negative niceness for a process as a regular user with firejail #339
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#339
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dirtybytes on GitHub (Apr 23, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/477
Likely not a huge security issue, but still.
According to this: http://linux.die.net/man/2/nice
And, indeed,
nice -n -20 /bin/bashwould start bash with 0 niceness value, informing you of the failure. However, a recently implemented--niceoption allows you to bypass it, setting the initial niceness of a process to -20, probably because firejail is SUID root. It looks like it can't be done from within the jail itself, but it still allows a regular user to do something he shouldn't be able to using this program.@netblue30 commented on GitHub (May 2, 2016):
Fixed, thank you for the bug.