mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1973] [information] Scenario of an attack #1324
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#1324
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 @g3ngr33n on GitHub (May 31, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1973
Hello,
I cannot figure out what would happen in the following scenario
Configuration
Firefox run inside a firejail sandbox which have the parameters --apparmor
Firefox doesn't have an apparmor profile, only firejail.
Scenario
An attacker exploit a vulnerability inside Firefox to gain access on the system, the attacker known a 0day that allow him to escape the firejail sandbox
What happen at this point ?
Thanks
@SkewedZeppelin commented on GitHub (May 31, 2018):
From what I understand when a profile uses AppArmor, Firejail will enable that early on during sandbox creation so AppArmor can protect the system if Firejail is compromised.
A hypothetical attack could be as follows
I might be completely wrong, and someone else can probably explain it better.
@g3ngr33n commented on GitHub (May 31, 2018):
Thank you for this fast reply.
If you're answer is correct and I understand it correctly, there is no need to write a firefox profile apparmor in addition of the firejail one.
@Vincent43 commented on GitHub (Jun 4, 2018):
Firejail use generic apparmor profile which can cover (depends on distro) some things like dbus,ptrace, non-standard network access, noexec /home, writing to /proc and /sys independently of firejail own sandbox. You can make your own specfic firefox apparmor profile or use some you find o the web but then it's better to use it alone without firejail.
@FOSSONLY commented on GitHub (Jun 25, 2018):
This will never happen if:
A 0-day exploit is also not directly able to circumvent security-features. You need mostly a very powerful exploit, or many of them in combination to get successful access. And if an attacker is getting direct access via kernel-exploit, there is no difference between Firejail or AppArmor. You lose.
If there is no AppArmor-Profile in extension to Firejail, there exist no additional security-layer if Firejail gets bypassed. And for any bypass of Seccomp/Namespaces you need an kernel-exploit, who possibly can bypass AppArmor too.
But don't worry, the Kernel-Self-Protection-Project makes very good efforts. Also additional LSM-Modules like the Linux-Kernel-Runtime-Guard, will be an interesting security-layer in future.
So the best strategy is always prevention.
@g3ngr33n commented on GitHub (Jun 27, 2018):
Thanks for those information, will start to write a profile apparmor for firefox and other app and use it independantly of Firejail.
About LKRG, I made a post few days ago (see https://forums.gentoo.org/viewtopic-p-8231330.html?sid=43c8a000e3a5b2b3e7dab91706b138c5#8231330), doesn't seem to work yet on Gentoo but it is definitively a security feature that I will use
KSPP is alright, I can only thanks free security work provided by the community
@Vincent43 commented on GitHub (Jun 27, 2018):
I think the question was answered. Nothing to do here.