FirefoxWeb browser · Mozilla
CVE-2024-0754
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 · uneditedSome WASM source files could have caused a crash when loaded in devtools. This vulnerability affects Firefox < 122.
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 confidenceA vulnerability in Firefox devtools allows specially crafted WASM (WebAssembly) source files to trigger a crash when loaded in the developer tools. This is a denial-of-service vulnerability affecting Firefox versions prior to 122.
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
< 122.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 if Firefox is installedLook for Firefox in your applications folder, or run 'which firefox' or 'firefox --version' in a terminalAffected if Firefox is not found on the system, this CVE does not apply
-
Determine the installed Firefox versionRun 'firefox --version' in a terminal, or open Firefox and go to Help > About Firefox to view the version numberAffected if The displayed version is lower than 122.0 (for example, 121.0, 120.0, etc.)
-
Verify the devtools usage contextThis vulnerability specifically affects the developer tools when loading WASM source files. Check if devtools are used for WebAssembly debugging in your environmentAffected if Devtools are used to inspect WASM files and the Firefox version is below 122.0
-
Compare version against affected rangeMozilla Firefox versions prior to 122.0 are affected. If your version shows 121.x or any lower number, it falls within the vulnerable rangeAffected if Installed version is less than 122.0
You are affected if Firefox is installed and the version number is below 122.0, especially if you use developer tools to inspect WebAssembly files.
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 · scoped122.0
Update Firefox to version 122 or later to receive the fix for this crash vulnerability.
Firefox 122.0
- Check current Firefox version by navigating to about:firefox or going to Help > About Firefox
- Download Firefox 122.0 or later from the official Mozilla website (www.mozilla.org) or use your system's package manager to update
- Close all Firefox instances before installing the update
- Install the updated Firefox version
- Restart Firefox and verify the version is 122.0 or higher in about:firefox
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0754 — 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-0754 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