# CVE-2017-5206: Security feature bypass in n/a

> Attackers can bypass Firejail seccomp sandbox protections using the --allow-debuggers argument on older Linux kernels.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5206, GHSA-cj78-6w9j-286h, UBUNTU-CVE-2017-5206

## What is CVE-2017-5206?

CVE-2017-5206 is a critical vulnerability in n/a, published on 23 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2017-5206?

It affects 1 product.


Products: Firejail Project Firejail.

## How do I fix CVE-2017-5206?

Upgrade to a fixed version.

## Is CVE-2017-5206 being exploited?

There is no known exploitation of CVE-2017-5206 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-12589](https://insights.sbomify.com/CVE-2019-12589/): Security feature bypass in n/a (high 8.8)
- [CVE-2017-5180](https://insights.sbomify.com/CVE-2017-5180/): Privilege escalation in n/a (high 8.8)
- [CVE-2017-5940](https://insights.sbomify.com/CVE-2017-5940/): Privilege escalation in n/a (high 8.8)
- [CVE-2016-9016](https://insights.sbomify.com/CVE-2016-9016/): Security feature bypass in n/a (high 8.8)
- [CVE-2019-12499](https://insights.sbomify.com/CVE-2019-12499/): Privilege escalation in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5206 and fix it if it is affected.

What it is: CVE-2017-5206 is a critical vulnerability in n/a, published on 23 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5206 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5206/ (Markdown: https://insights.sbomify.com/CVE-2017-5206/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5206
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5206
- OSV: https://osv.dev/vulnerability/CVE-2017-5206

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5206/
Summaries are generated and may contain mistakes; the official description above is the record.