Parent-process crash via shared-memory offset race
Published Jan 8, 2020 · Updated Aug 5, 2024
Memory corruption in Mozilla Firefox before 72 and Firefox ESR before 68.4 allows attackers to crash the parent process on Windows. SharedMemIPCServer::Init reads a shared channel_base value after exposing the memory handle, allowing a renderer race to corrupt channel_buffer. Exploitation requires code execution in a sandboxed renderer; a crash was demonstrated, but parent-process code execution was not established.
Summary
What happened
Memory corruption in Mozilla Firefox before 72 and Firefox ESR before 68.4 allows attackers to crash the parent process on Windows. SharedMemIPCServer::Init reads a shared channel_base value after exposing the memory handle, allowing a renderer race to corrupt channel_buffer. Exploitation requires code execution in a sandboxed renderer; a crash was demonstrated, but parent-process code execution was not established.
The record
- CVE
- CVE-2019-17015
- Published
- Jan 8, 2020
- Updated
- Aug 5, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-787, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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 72
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.
Public exploit references
- Bugzilla race.zip 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