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

> A compromised thumbnailer can escape the bubblewrap sandbox via TIOCSTI ioctl, allowing attackers to execute code outside the confined environment.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:H/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:** 22 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11461, GHSA-jjgg-8c74-rh96, openSUSE-SU-2024:11076-1

## What is CVE-2019-11461?

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

### Official description

An issue was discovered in GNOME Nautilus 3.30 prior to 3.30.6 and 3.32 prior to 3.32.1. A compromised thumbnailer may escape the bubblewrap sandbox used to confine thumbnailers by using the TIOCSTI ioctl to push characters into the input buffer of the thumbnailer's controlling terminal, allowing an attacker to escape the sandbox if the thumbnailer has a controlling terminal. This is due to improper filtering of the TIOCSTI ioctl on 64-bit systems, similar to CVE-2019-10063.

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

It affects 1 product.


Products: Gnome Nautilus.

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

Upgrade to a fixed version.

## Is CVE-2019-11461 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11461 and fix it if it is affected.

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

## Sources

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

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