Browser crash via mishandled WebAssembly tail calls
Published Jan 23, 2024 · Updated May 22, 2025
A DevTools WebAssembly flaw in Mozilla Firefox before 122 allows remote attackers to crash the browser via a crafted WASM source file. The debugger uses the wrong LeaveFrame marker for tail calls and tracks reference-type results that must be discarded, ending in invalid JSObject::getClass access. Exploitation requires a user to load the crafted source in DevTools, and the demonstrated consequence is a browser crash.
Summary
What happened
A DevTools WebAssembly flaw in Mozilla Firefox before 122 allows remote attackers to crash the browser via a crafted WASM source file. The debugger uses the wrong LeaveFrame marker for tail calls and tracks reference-type results that must be discarded, ending in invalid JSObject::getClass access. Exploitation requires a user to load the crafted source in DevTools, and the demonstrated consequence is a browser crash.
The record
- CVE
- CVE-2024-0754
- Published
- Jan 23, 2024
- Updated
- May 22, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-248
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- May 22, 2025Record 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
- Mozilla WebAssembly debugger crash testcaseproof 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