FirefoxWeb browser · Mozilla
CVE-2024-6613
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces. This vulnerability affects Firefox < 128 and Thunderbird < 128.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe frame iterator in Firefox and Thunderbird can enter an infinite loop when processing certain WebAssembly frames, causing incorrect stack traces. This is a logic error in the wasm frame handling code that affects versions prior to 128.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FirefoxWeb browser
< 128.0< 128.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionOpen Firefox, go to Help > About Firefox, or run 'firefox --version' from command line. Note the displayed version number.Affected if The installed version is less than 128.0 (for example, 127.x, 127.0.1, etc.)
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' from command line. Note the displayed version number.Affected if The installed version is less than 128.0 (for example, 127.x, 127.0.1, etc.)
-
Confirm WebAssembly usage contextDetermine if the browser or application processes WebAssembly content. This could be through visiting websites using WASM modules, running local WASM applications, or processing WASM attachments.Affected if WebAssembly is actively used AND the product version is below 128.0
You are affected if either Firefox or Thunderbird is installed at a version lower than 128.0 and the application processes WebAssembly content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped128.0
Update Firefox and Thunderbird to version 128 or later to obtain the patched frame iterator code.
Firefox 128.0 and Thunderbird 128.0
- Back up any important data (bookmarks, passwords, emails in Thunderbird)
- Update Firefox to version 128.0 or later by checking Help > About Firefox or visiting mozilla.org/firefox
- Update Thunderbird to version 128.0 or later by checking Help > About Thunderbird or visiting mozilla.org/thunderbird
- Restart the browser/application after the update completes
- Verify the update was successful by checking the version number in About dialog
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6613 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data