mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #802] Breakout through terminal #545
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#545
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 @DavidBrandly on GitHub (Sep 22, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/802
Executing
mate-terminal -e "sudo su -c 'whoami > /file'"in a firejail session creates a file under/as root.@netblue30 commented on GitHub (Sep 22, 2016):
mate-terminal and a bunch of other terminals are disabled in /etc/firejail/disable-programs.inc. A real exploit going directly to DBus and exploiting gnome-terminal is described here: https://github.com/netblue30/firejail/issues/796. It should work the same for mate-terminal.
@Fred-Barclay commented on GitHub (Sep 22, 2016):
@DavidBrandly As netblue30 mentioned,
mate-terminalhas been blacklisted in the last two releases of firejail due to this very behavior. Do you perchance have an older version of firejail?Firejail 0.9.43 (current development version):
@DavidBrandly commented on GitHub (Sep 23, 2016):
@Fred-Barclay I hadn't noticed that apt has been holding back firejail. It's updated now, thanks for the help!
@Fred-Barclay commented on GitHub (Sep 23, 2016):
@DavidBrandly No worries, mate. 😄