Firejail vulnerabilities

Firejail allows the use of --chroot when seccomp is not supported, which might allow local users to gain privileges.

Firejail does not properly clean environment variables, allowing local users to gain elevated privileges.

Firejail uses weak permissions for /dev/shm/firejail and possibly other files, allowing local users to gain privileges.

Firejail uses 0777 permissions when mounting directories such as /dev, /dev/shm, /var/tmp, and /var/lock, allowing local users to gain elevated privileges.

Firejail uses 0777 permissions when mounting /tmp, which allows local users to gain privileges.

Firejail does not restrict access to --tmpfs, allowing local users to gain privileges, as demonstrated by mounting over /etc.

Firejail before 0.9.44.4, when running a bandwidth command, allows local users to gain root privileges via the --shell argument.

Firejail versions before 0.9.44.6 and 0.9.38.x LTS before 0.9.38.10 LTS do not comprehensively address dotfile cases, allowing local users to conduct sandbox-escape attacks via symlinks and the --private option.

Firejail before 0.9.44.4 and 0.9.38.x LTS before 0.9.38.8 LTS does not consider the .Xauthority case during its attempt to prevent accessing user files with an euid of zero, allowing local users to conduct sandbox-escape attacks via symlinks and the --private option.

Firejail version 0.9.38.4 allows local users to execute arbitrary commands outside of the sandbox via a crafted TIOCSTI ioctl call.

Firejail before 0.9.44.4, when running on a Linux kernel before 4.8, allows context-dependent attackers to bypass a seccomp-based sandbox protection mechanism via the --allow-debuggers argument.