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

> Attackers can escape the bubblewrap sandbox by injecting terminal input via TIOCSTI, leading to privilege escalation or code execution in the parent session.

- **Severity:** Critical 10.0 (`CVSS:3.0/AV:N/AC:L/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:** 29 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-5226, GHSA-m28g-vfcm-85ff, openSUSE-SU-2024:12835-1

## What is CVE-2017-5226?

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

### Official description

When executing a program via the bubblewrap sandbox, 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 sandbox.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Projectatomic Bubblewrap.

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

Apply the vendor's patch.

## Is CVE-2017-5226 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12439](https://insights.sbomify.com/CVE-2019-12439/): Race condition in n/a (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5226 is a critical vulnerability in n/a, published on 29 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-5226 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-5226/ (Markdown: https://insights.sbomify.com/CVE-2017-5226/index.md)
```

## Sources

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

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