Incorrect stack traces via repeated Wasm frames
Published Jul 9, 2024 · Updated Oct 30, 2025
Incorrect stack-frame iteration in Mozilla Firefox and Thunderbird before 128 allows attackers to produce wrong traces via crafted Wasm. JSJitFrameIter wrongly applies bailout data to JSJitToWasm transition frames, restarting at the bailout frame instead of advancing to the next JavaScript frame. Execution requires Wasm-to-JavaScript calls, promises, saved stacks, and an exception during bailout; release builds cap the duplicated trace at 128 frames.
Summary
What happened
Incorrect stack-frame iteration in Mozilla Firefox and Thunderbird before 128 allows attackers to produce wrong traces via crafted Wasm. JSJitFrameIter wrongly applies bailout data to JSJitToWasm transition frames, restarting at the bailout frame instead of advancing to the next JavaScript frame. Execution requires Wasm-to-JavaScript calls, promises, saved stacks, and an exception during bailout; release builds cap the duplicated trace at 128 frames.
The record
- CVE
- CVE-2024-6613
- Published
- Jul 9, 2024
- Updated
- Oct 30, 2025
- Vendor
- Mozilla
- Product
- Firefox
- Classifications
- CWE-209
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 30, 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 <128
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- frameptr_has_cached_saved_frame.js reproducerproof 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