FirefoxWeb browser · Mozilla
CVE-2024-3852
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 · uneditedGetBoundName could return the wrong version of an object when JIT optimizations were applied. This vulnerability affects Firefox < 125, Firefox ESR < 115.10, and Thunderbird < 115.10.
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 bug in the SpiderMonkey JavaScript engine's JIT compiler causes GetBoundName to return an incorrect version of an object during bound function name resolution. This memory confusion could allow attackers to access stale object references, potentially leading to arbitrary code execution.
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
< 115.10< 125.0< 115.10CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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 versionNavigate to about:support in Firefox or go to Help > About Firefox. Locate the 'Version' field.Affected if Version is below 115.10 or below 125.0 (any version before 125.0 is affected)
-
Check Thunderbird versionNavigate to about:support in Thunderbird or go to Help > About Thunderbird. Locate the 'Version' field.Affected if Version is below 115.10
-
Confirm JIT compiler is enabledIn Firefox or Thunderbird, navigate to about:config and search for 'javascript.options.jit'. The setting 'javascript.options.jit' should be present and set to true.Affected if JIT is disabled, the specific exploitation pathway is not available, though the code defect still exists in the engine
You are affected if you run Firefox versions below 125.0 (or below 115.10 for ESR channels) or Thunderbird versions below 115.10, with the JIT compiler enabled (default state).
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 · scoped115.10125.0
Upgrade to Firefox 125+, Firefox ESR 115.10+, or Thunderbird 115.10+ to obtain the patched JavaScript engine.
Firefox 125.0, Firefox ESR 115.10, or Thunderbird 115.10
- Back up any important data (bookmarks, passwords, extensions) from the current Firefox/Thunderbird installation
- For Firefox: Navigate to the Firefox menu > Help > About Firefox, or go to https://www.mozilla.org/firefox/ and download version 125.0 or later
- For Firefox ESR: Download version 115.10 or later from https://www.mozilla.org/firefox/enterprise/
- For Thunderbird: Navigate to the Thunderbird menu > Help > About Thunderbird, or go to https://www.thunderbird.net/ and download version 115.10 or later
- Restart the application after the update completes
- Verify the installed version matches or exceeds the fixed release (Firefox ≥125.0, Firefox ESR ≥115.10, Thunderbird ≥115.10)
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-3852 — 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-3852 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