🛡️ CVE-2022-31214
🟠 CVSS 7.8 — High ✅ No Known Exploit CWE-269 NVD
7.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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.

Details

Severity HIGH
CVSS Score 7.8
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE CWE-269
Public Exploit ✅ No
Source NVD
Published 2022-06-09
Updated 2026-06-08
Modified 2024-11-21

Affected Packages

Software From version Fixed in
debian-linux — —
fedora — —
firejail — —

References

Release Notes, Third Party Advisory https://firejail.wordpress.com/download-2/release-notes/
Mailing List, Patch, Third Party Advisory https://www.openwall.com/lists/oss-security/2022/06/08/10
Release Notes, Third Party Advisory https://firejail.wordpress.com/download-2/release-notes/
Mailing List, Patch, Third Party Advisory https://www.openwall.com/lists/oss-security/2022/06/08/10

Similar Threats

Vulnerability Monitoring

Stay informed about vulnerabilities in your stack

BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.