dbcve.org
Debian LinuxOperating system · Debian

CVE-2020-17367

HIGH · 7.8 CVSS v3.1 Published 2020-08-11
Fix available
A fix is available. Upgrade to after 0.9.62 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Firejail through 0.9.62 does not honor the -- end-of-options indicator after the --output option, which may lead to command injection.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Firejail through 0.9.62 contains a command injection vulnerability in its argument parsing logic. The -- end-of-options delimiter is not properly honored after the --output option, allowing attacker-controlled arguments to be interpreted as additional options rather than as literal arguments to the sandboxed command. This can lead to arbitrary command execution by bypassing the intended sandboxing mechanism.

MitigationUpgrade Firejail to a patched version beyond 0.9.62, or if no upgrade is available, avoid using the --output option with untrusted/sanitized input and implement strict input validation on all arguments passed to Firejail.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 10.0= 9.0
FedoraOperating system
Affected:= 31= 32
FirejailApplication
Affected:<= 0.9.62
LeapOperating system
Affected:= 15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Firejail version
    Run 'firejail --version' or check package manager (dpkg -l firejail, rpm -q firejail)
    Affected if Version is 0.9.62 or lower
  2. Identify scripts or configs using --output option
    Search for '--output' in /etc/firejail, ~/.config/firejail, and any shell scripts that invoke firejail (grep -r '--output' /etc/firejail ~/.config 2>/dev/null)
    Affected if The --output option is used with user-controlled or untrusted arguments
  3. Check for proper delimiter usage with --output
    Review firejail command lines to see if '--' delimiter appears after --output and before the sandboxed command arguments
    Affected if The '--' delimiter is missing between --output and the command arguments
  4. Verify argument handling in custom profiles
    Inspect custom .profile files in ~/.config/firejail/ for any --output usage and how arguments are passed
    Affected if Profiles pass arguments to firejail without proper quoting or delimiter handling

You are affected if Firejail version is 0.9.62 or lower AND the --output option is used with arguments that could be controlled by untrusted input without proper '--' delimiter protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 0.9.62
Interim mitigation

Upgrade Firejail to a patched version beyond 0.9.62, or if no upgrade is available, avoid using the --output option with untrusted/sanitized input and implement strict input validation on all arguments passed to Firejail.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-17367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-17367 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data