# CVE-2019-10063: Security feature bypass in n/a > Attackers can bypass Flatpak sandbox restrictions on 64-bit systems to execute arbitrary commands outside the sandbox via a flawed seccomp filter. - **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/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:** 26 Mar 2019 - **Updated:** 4 Aug 2024 - **Also known as:** CLEANSTART-2024-SG68553, DEBIAN-CVE-2019-10063, GHSA-mc9j-733x-89cx, OESA-2021-1380, RHSA-2019:1024, RHSA-2019:1143, UBUNTU-CVE-2019-10063 ## What is CVE-2019-10063? CVE-2019-10063 is a critical vulnerability in n/a, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Flatpak before 1.0.8, 1.1.x and 1.2.x before 1.2.4, and 1.3.x before 1.3.1 allows a sandbox bypass. Flatpak versions since 0.8.1 address CVE-2017-5226 by using a seccomp filter to prevent sandboxed apps from using the TIOCSTI ioctl, which could otherwise be used to inject commands into the controlling terminal so that they would be executed outside the sandbox after the sandboxed app exits. This fix was incomplete: on 64-bit platforms, the seccomp filter could be bypassed by an ioctl request number that has TIOCSTI in its 32 least significant bits and an arbitrary nonzero value in its 32 most significant bits, which the Linux kernel would treat as equivalent to TIOCSTI. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2019-10063? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `flatpak` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.2-5.el7_6 | | `flatpak-builder` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.0-5.el7_6 | | `flatpak-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.2-5.el7_6 | | `flatpak-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.2-5.el7_6 | | `flatpak-libs` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.2-5.el7_6 | | `flatpak` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.2-5.el7_6 | | `flatpak-builder` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.0-5.el7_6 | | `flatpak-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.2-5.el7_6 | | `flatpak-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.2-5.el7_6 | | `flatpak-libs` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.2-5.el7_6 | | `flatpak` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.2-5.el7_6 | | `flatpak-builder` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.0-5.el7_6 | | `flatpak-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.2-5.el7_6 | | `flatpak-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.2-5.el7_6 | | `flatpak-libs` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.2-5.el7_6 | | `flatpak` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.2-5.el7_6 | | `flatpak-builder` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.0-5.el7_6 | | `flatpak-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.2-5.el7_6 | | `flatpak-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.2-5.el7_6 | | `flatpak-libs` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.2-5.el7_6 | | `flatpak` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.6-3.el8_0 | | `flatpak-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.6-3.el8_0 | | `flatpak-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.6-3.el8_0 | | `flatpak-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.6-3.el8_0 | | `flatpak-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.0.6-3.el8_0 | Products: Flatpak Flatpak. ## How do I fix CVE-2019-10063? Upgrade to a fixed version. ## Is CVE-2019-10063 being exploited? There is no known exploitation of CVE-2019-10063 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2023-28100](https://insights.sbomify.com/CVE-2023-28100/): TIOCLINUX can send commands outside sandbox if running on a virtual console (critical 10.0) - [CVE-2026-34078](https://insights.sbomify.com/CVE-2026-34078/): Flatpak has a complete sandbox escape leading to host file access and code execution in the host context (critical 9.3) - [CVE-2018-6560](https://insights.sbomify.com/CVE-2018-6560/): Security feature bypass in n/a (high 8.8) - [CVE-2026-34079](https://insights.sbomify.com/CVE-2026-34079/): Flatpak affected by arbitrary file deletion on the host filesystem (high 8.7) - [CVE-2023-28101](https://insights.sbomify.com/CVE-2023-28101/): Flatpak metadata with ANSI control codes can cause misleading terminal output (medium 5.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-10063 and fix it if it is affected. What it is: CVE-2019-10063 is a critical vulnerability in n/a, published on 26 Mar 2019. 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-2019-10063 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-10063/ (Markdown: https://insights.sbomify.com/CVE-2019-10063/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-10063 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-10063 - OSV: https://osv.dev/vulnerability/CVE-2019-10063 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-10063/ Summaries are generated and may contain mistakes; the official description above is the record.