CVE-2017-5206

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.

Published: 2017-03-23 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-5206 is rated Moderate Risk (62.6/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 1.94%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-5206

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 2.41% 1.94% -0.47%
2 2025-03-30 4.51% 2.41% -2.10%
3 2025-03-29 — 4.51% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5206

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.0 3.0 CRITICAL
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 6.0 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-5206

OS Trackers for CVE-2017-5206

vendor priority summary link
debian not yet assigned CVE-2017-5206 not yet assigned priority: Debian including 1 source packages (firejail), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): resolved 4. https://security-tracker.debian.org/tracker/CVE-2017-5206
gentoo normal CVE-2017-5206: 1 GLSA(s) (201701-62), 2 atom(s) (sys-apps/firejail, sys-apps/firejail-lts); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-5206
ubuntu medium CVE-2017-5206 medium priority: Ubuntu including 1 source packages (firejail), 23 status rows across 23 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 18, DNE 2, ignored 1, needed 1, released 1. https://ubuntu.com/security/CVE-2017-5206

Affected software / configurations for CVE-2017-5206

Vendor Product Version Raw CPE
firejail_project firejail < 0.9.44.4 cpe:2.3:a:firejail_project:firejail:*:*:*:*:*:*:*:*

References for CVE-2017-5206

cvelogic Threat Intelligence