NVD / CVE Program· CNA mitre

CVE-2022-31214: A Privilege Context Switching issue was discovered in join.c in Firejail 0.9.68.

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: firejail (Debian:10) 0.9.58.2-2+deb10u3; firejail (Debian:11) 0.9.64.4-2+deb11u1; firejail (Debian:12) 0.9.68-4.

Low priority for now. Upgrade to firejail (Debian:10) 0.9.58.2-2+deb10u3; firejail (Debian:11) 0.9.64.4-2+deb11u1; firejail (Debian:12) 0.9.68-4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.8 · v3.1—No exploit Fix available

Local privilege escalation

Published: Jun 9, 2022
Updated: Jun 17, 2026
EPSS: 0.4% · 34th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
firejail project	firejail	cpe:2.3:a:firejail_project:firejail
fedoraproject	fedora	cpe:2.3:o:fedoraproject:fedora
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux10.0
debian debian linux9.0
fedoraproject fedora35
fedoraproject fedora36
fedoraproject fedora37
firejail project firejail0.9.68

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:10	firejail	before 0.9.58.2-2+deb10u3	0.9.58.2-2+deb10u3
Debian:11	firejail	before 0.9.64.4-2+deb11u1	0.9.64.4-2+deb11u1
Debian:12	firejail	before 0.9.68-4	0.9.68-4
Debian:9	firejail	before 0.9.58.2-2+deb9u1	0.9.58.2-2+deb9u1
openSUSE:Leap 15.3	firejail	before 0.9.70-bp153.2.6.1	0.9.70-bp153.2.6.1
openSUSE:Leap 15.4	firejail	before 0.9.70-bp154.2.3.1	0.9.70-bp154.2.3.1
SUSE:Package Hub 15 SP3	firejail	before 0.9.70-bp153.2.6.1	0.9.70-bp153.2.6.1
SUSE:Package Hub 15 SP4	firejail	before 0.9.70-bp154.2.3.1	0.9.70-bp154.2.3.1

Same product

firejail project: all records

Other highest-scoring records for the same primary product.

CVE-2020-17368Firejail through 0.9.62 mishandles shell metacharacters during use of the --output or --output-stderr option, which may lead to command inje
40Plan
CVE-2019-12589In Firejail before 0.9.60, seccomp filters are writable inside the jail, leading to a lack of intended seccomp restrictions for a process th
35Monitor
CVE-2017-5940Firejail before 0.9.44.6 and 0.9.38.x LTS before 0.9.38.10 LTS does not comprehensively address dotfile cases during its attempt to prevent
35Monitor

Published before and after this one in the same product

← EarlierCVE-2019-12499May 31, 2019 · 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
33Monitor
← EarlierCVE-2020-17367Aug 11, 2020 · Firejail through 0.9.62 does not honor the -- end-of-options indicator after the --output option, which may lead to command injection.
31Monitor
← EarlierCVE-2021-26910Feb 8, 2021 · Firejail before 0.9.64.4 allows attackers to bypass intended access restrictions because there is a TOCTOU race condition between a stat ope
28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:firejail	0.9.68-4 · Debian:12	Package registry (OSV)
opensuse:firejail	0.9.70-bp153.2.6.1 · openSUSE:Leap 15.3	Package registry (OSV)
suse:firejail	0.9.70-bp153.2.6.1 · SUSE:Package Hub 15 SP3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

firejail.wordpress.com/download-2/release-notes/

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records