# CVE-2019-12589: Security feature bypass in n/a

> Attackers can modify writable seccomp filters in Firejail to bypass intended security restrictions for processes joining the jail.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-12589, GHSA-q9v9-56wp-f76g, UBUNTU-CVE-2019-12589

## What is CVE-2019-12589?

CVE-2019-12589 is a high-severity vulnerability in n/a, published on 3 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Firejail before 0.9.60, seccomp filters are writable inside the jail, leading to a lack of intended seccomp restrictions for a process that is joined to the jail after a filter has been modified by an attacker.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2019-12589?

It affects 1 product.


Products: Firejail Project Firejail.

## How do I fix CVE-2019-12589?

Upgrade to a fixed version.

## Is CVE-2019-12589 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-5206](https://insights.sbomify.com/CVE-2017-5206/): Security feature bypass in n/a (critical 9.0)
- [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-2019-12589 and fix it if it is affected.

What it is: CVE-2019-12589 is a high-severity vulnerability in n/a, published on 3 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12589 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-2019-12589/ (Markdown: https://insights.sbomify.com/CVE-2019-12589/index.md)
```

## Sources

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

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