Show filters
18 Total Results
Displaying 1-10 of 18
Sort by:
Attacker Value
Unknown

CVE-2022-31214

Disclosure Date: June 09, 2022 (last updated November 08, 2023)
A Privilege Context Switching issue was discovered in join.c in Firejail 0.9.68. By crafting a bogus Firejail container that is accepted by the Firejail setuid-root program as a join target, a local attacker can enter an environment in which the Linux user namespace is still the initial user namespace, the NO_NEW_PRIVS prctl is not activated, and the entered mount namespace is under the attacker's control. In this way, the filesystem layout can be adjusted to gain root privileges through execution of available setuid-root binaries such as su or sudo.
Attacker Value
Unknown

CVE-2021-26910

Disclosure Date: February 08, 2021 (last updated November 28, 2024)
Firejail before 0.9.64.4 allows attackers to bypass intended access restrictions because there is a TOCTOU race condition between a stat operation and an OverlayFS mount operation.
Attacker Value
Unknown

CVE-2020-17367

Disclosure Date: August 11, 2020 (last updated February 21, 2025)
Firejail through 0.9.62 does not honor the -- end-of-options indicator after the --output option, which may lead to command injection.
Attacker Value
Unknown

CVE-2020-17368

Disclosure Date: August 11, 2020 (last updated February 21, 2025)
Firejail through 0.9.62 mishandles shell metacharacters during use of the --output or --output-stderr option, which may lead to command injection.
Attacker Value
Unknown

CVE-2019-12589

Disclosure Date: June 03, 2019 (last updated November 08, 2023)
In Firejail before 0.9.60, seccomp filters are writable inside the jail, leading to a lack of intended seccomp restrictions for a process that is joined to the jail after a filter has been modified by an attacker.
0
Attacker Value
Unknown

CVE-2019-12499

Disclosure Date: May 31, 2019 (last updated November 08, 2023)
Firejail before 0.9.60 allows truncation (resizing to length 0) of the firejail binary on the host by running exploit code inside a firejail sandbox and having the sandbox terminated. To succeed, certain conditions need to be fulfilled: The jail (with the exploit code inside) needs to be started as root, and it also needs to be terminated as root from the host (either by stopping it ungracefully (e.g., SIGKILL), or by using the --shutdown control command). This is similar to CVE-2019-5736.
0
Attacker Value
Unknown

CVE-2016-10123

Disclosure Date: April 13, 2017 (last updated November 26, 2024)
Firejail allows --chroot when seccomp is not supported, which might allow local users to gain privileges.
0
Attacker Value
Unknown

CVE-2016-10119

Disclosure Date: April 13, 2017 (last updated November 26, 2024)
Firejail uses 0777 permissions when mounting /tmp, which allows local users to gain privileges.
0
Attacker Value
Unknown

CVE-2016-10118

Disclosure Date: April 13, 2017 (last updated November 26, 2024)
Firejail allows local users to truncate /etc/resolv.conf via a chroot command to /.
0
Attacker Value
Unknown

CVE-2016-10121

Disclosure Date: April 13, 2017 (last updated November 26, 2024)
Firejail uses weak permissions for /dev/shm/firejail and possibly other files, which allows local users to gain privileges.
0