Sandbox escape via attacker-controlled synced preferences
Published Jan 8, 2020 · Updated Aug 4, 2024
Sandbox escape in Firefox before 69 and Firefox ESR before 60.9 or 68.1 allows attackers to disable content-process isolation. Firefox Sync accepted attacker-created services.sync.prefs.sync.* control preferences, then applied synchronized sandbox and process-model settings locally. Exploitation requires a separate content-process compromise, forced sign-in to an attacker-controlled Sync account, and a triggered crash.
Summary
What happened
Sandbox escape in Firefox before 69 and Firefox ESR before 60.9 or 68.1 allows attackers to disable content-process isolation. Firefox Sync accepted attacker-created services.sync.prefs.sync.* control preferences, then applied synchronized sandbox and process-model settings locally. Exploitation requires a separate content-process compromise, forced sign-in to an attacker-controlled Sync account, and a triggered crash.
The record
- CVE
- CVE-2019-9812
- Published
- Jan 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 69
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Mozilla Bug 1538008 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo