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

> Attackers can escape LXC containers to the host system by injecting terminal input via TIOCSTI ioctl during lxc-attach execution.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-10124, GHSA-97h5-fmw5-r7vf, UBUNTU-CVE-2016-10124, USN-3375-1

## What is CVE-2016-10124?

CVE-2016-10124 is a high-severity vulnerability in n/a, published on 9 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Linux Containers (LXC) before 2016-02-22. When executing a program via lxc-attach, the nonpriv session can escape to the parent session by using the TIOCSTI ioctl to push characters into the terminal's input buffer, allowing an attacker to escape the container.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Linuxcontainers Lxc.

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

Apply the vendor's patch.

## Is CVE-2016-10124 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8649](https://insights.sbomify.com/CVE-2016-8649/): Path traversal in LXC before 1.0.9 and 2.x before 2.0.6 (critical 9.1)
- [CVE-2017-18641](https://insights.sbomify.com/CVE-2017-18641/): Supply chain in n/a (high 8.1)
- [CVE-2013-6441](https://insights.sbomify.com/CVE-2013-6441/): Privilege escalation in n/a (high 7.2)
- [CVE-2015-1331](https://insights.sbomify.com/CVE-2015-1331/): Path traversal in n/a (medium 4.9)
- [CVE-2015-1334](https://insights.sbomify.com/CVE-2015-1334/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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