# CVE-2019-11708: Mozilla Firefox and Thunderbird Sandbox Escape > Insufficient parameter vetting in IPC allows a compromised child process to force the parent to open web content, potentially leading to arbitrary code execution. - **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 23 May 2022 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Jul 2019 - **Updated:** 21 Oct 2025 - **Also known as:** ALPINE-CVE-2019-11708, DEBIAN-CVE-2019-11708, DSA-4474-1, GHSA-w2hj-6j62-2w9f, MGASA-2019-0202, SUSE-SU-2019:1682-1, SUSE-SU-2019:1684-1, UBUNTU-CVE-2019-11708, USN-4032-1, openSUSE-SU-2019:1595-1 ## What is CVE-2019-11708? CVE-2019-11708 is a critical vulnerability in Mozilla Firefox, published on 23 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Insufficient vetting of parameters passed with the Prompt:Open IPC message between child and parent processes can result in the non-sandboxed parent process opening web content chosen by a compromised child process. When combined with additional vulnerabilities this could result in executing arbitrary code on the user's computer. This vulnerability affects Firefox ESR < 60.7.2, Firefox < 67.0.4, and Thunderbird < 60.7.2. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2019-11708? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `MozillaFirefox` | SUSE:Enterprise Storage 4 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Enterprise Storage 5 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 60.7.2-3.48.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 60.7.2-3.48.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:OpenStack Cloud 7 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | SUSE:OpenStack Cloud 8 | All versions | 60.7.2-109.80.1 | | `MozillaFirefox` | openSUSE:Leap 15.1 | All versions | 60.7.2-lp151.2.7.1 | Products: Mozilla Firefox, Mozilla Thunderbird. ## How do I fix CVE-2019-11708? Upgrade to a fixed version. US federal agencies must fix it by 13 Jun 2022. ## Is CVE-2019-11708 being exploited? Yes. Attackers have exploited CVE-2019-11708 in the wild since at least 23 May 2022. Public exploit code: - Full exploit chain (CVE-2019-11708 & CVE-2019-9810) against Firefox on Windows 64-bit. (github_poc): https://github.com/0vercl0k/CVE-2019-11708 - Mozilla FireFox (Windows 10 x64) - Full Chain Client Side Attack (exploitdb) ## Other vulnerabilities in Mozilla Firefox - [CVE-2010-3765](https://insights.sbomify.com/CVE-2010-3765/): Mozilla Multiple Products Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2022-26486](https://insights.sbomify.com/CVE-2022-26486/): Mozilla Firefox Use-After-Free (critical 9.6, exploited in the wild) - [CVE-2022-26485](https://insights.sbomify.com/CVE-2022-26485/): Mozilla Firefox Use-After-Free (high 8.8, exploited in the wild) - [CVE-2019-11707](https://insights.sbomify.com/CVE-2019-11707/): Mozilla Firefox and Thunderbird Type Confusion (high 8.8, exploited in the wild) - [CVE-2020-6819](https://insights.sbomify.com/CVE-2020-6819/): Mozilla Firefox And Thunderbird Use-After-Free (high 8.1, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-11708 and fix it if it is affected. What it is: CVE-2019-11708 is a critical vulnerability in Mozilla Firefox, published on 23 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: Yes. Attackers have exploited CVE-2019-11708 in the wild since at least 23 May 2022. Affected product: Mozilla Firefox. 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-11708/ (Markdown: https://insights.sbomify.com/CVE-2019-11708/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11708 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11708 - OSV: https://osv.dev/vulnerability/CVE-2019-11708 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-11708/ Summaries are generated and may contain mistakes; the official description above is the record.