Browser crash via stale WebGL actor reference
Published Jan 7, 2021 · Updated Aug 4, 2024
Use-after-free in WebGL in Mozilla Firefox before 84 allows remote attackers to trigger a potentially exploitable browser crash. WebGL omits a lifecycle check before GetLifecycleProxy reads an IPC actor reference whose manager has already died, leaving the actor stale. A network-delivered WebGL workload requires no authentication; the confirmed consequence is a crash, while reliable code execution is not publicly demonstrated.
Summary
What happened
Use-after-free in WebGL in Mozilla Firefox before 84 allows remote attackers to trigger a potentially exploitable browser crash. WebGL omits a lifecycle check before GetLifecycleProxy reads an IPC actor reference whose manager has already died, leaving the actor stale. A network-delivered WebGL workload requires no authentication; the confirmed consequence is a crash, while reliable code execution is not publicly demonstrated.
The record
- CVE
- CVE-2020-26972
- Published
- Jan 7, 2021
- Updated
- Aug 4, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 7, 2021CVE 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=unspecified <84
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
No public exploit references are available in this record.
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