Browser crash via JIT wild-pointer dereference
Published Jan 23, 2024 · Updated Sep 10, 2024
Wild-pointer dereference in Firefox before 122 allows remote attackers to crash the browser through JIT-compiled JavaScript. During an inlined constructor call, the baseline inline cache reloads a spilled ICStubReg after garbage collection clones the stub and updates its frame, causing a stale ICScript pointer read. A crafted JavaScript workload must trigger JIT-code disposal and page reuse during garbage collection; successful exploitation interrupts the browser process.
Summary
What happened
Wild-pointer dereference in Firefox before 122 allows remote attackers to crash the browser through JIT-compiled JavaScript. During an inlined constructor call, the baseline inline cache reloads a spilled ICStubReg after garbage collection clones the stub and updates its frame, causing a stale ICScript pointer read. A crafted JavaScript workload must trigger JIT-code disposal and page reuse during garbage collection; successful exploitation interrupts the browser process.
The record
- CVE
- CVE-2024-0744
- Published
- Jan 23, 2024
- Updated
- Sep 10, 2024
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-119, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Sep 10, 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 <122
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
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