# CVE-2016-10123: Privilege escalation in n/a

> Local users can gain privileges in Firejail when seccomp is unsupported and chroot is used, requiring a patched version.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/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:** 13 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-10123, GHSA-ff55-xjrc-r379

## What is CVE-2016-10123?

CVE-2016-10123 is a high-severity vulnerability in n/a, published on 13 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Firejail allows --chroot when seccomp is not supported, which might allow local users to gain privileges.

Weakness: CWE-264

## Which versions are affected by CVE-2016-10123?

It affects 1 product.


Products: Firejail Project Firejail.

## How do I fix CVE-2016-10123?

Apply the vendor's patch.

## Is CVE-2016-10123 being exploited?

There is no known exploitation of CVE-2016-10123 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-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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10123 and fix it if it is affected.

What it is: CVE-2016-10123 is a high-severity vulnerability in n/a, published on 13 Apr 2017. 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-2016-10123 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-2016-10123/ (Markdown: https://insights.sbomify.com/CVE-2016-10123/index.md)
```

## Sources

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

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