CVE-2023-25751
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 · uneditedSometimes, when invalidating JIT code while following an iterator, the newly generated code could be overwritten incorrectly. This could lead to a potentially exploitable crash. This vulnerability affects Firefox < 111, Firefox ESR < 102.9, and Thunderbird < 102.9.
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 race condition in Firefox's SpiderMonkey JIT compiler allows newly generated JIT code to be incorrectly overwritten when invalidating JIT code while following an iterator. This memory corruption during JIT code management can lead to a potentially exploitable crash.
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< 111.0< 102.9< 102.9CVSS 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.
-
Identify the installed Mozilla productCheck which application is installed: Firefox, Firefox ESR, or Thunderbird. In Windows, look in Program Files or the application icon. On Linux, check the package name (firefox, firefox-esr, thunderbird). On macOS, check /Applications for Firefox.app or Thunderbird.app.Affected if The product is Firefox, Firefox ESR, or Thunderbird - any of these three are affected by this CVE.
-
Determine the installed version numberFor Firefox: Enter 'about:support' in the address bar and look at the 'Version' field. For Thunderbird: Enter 'about:support' and check the version. On command line: 'firefox --version', 'thunderbird --version', or check the package manager (dpkg -r, rpm -q, etc.).Affected if The version is below 111.0 for Firefox, below 102.9 for Firefox ESR, or below 102.9 for Thunderbird.
-
Verify if SpiderMonkey JIT is enabledIn Firefox address bar, enter 'about:config' and search for 'jit'. Check if javascript.options.jit' is set to true. Also check 'javascript.options.baselinejit' and 'javascript.options.ion' - these control JIT compilation. For Thunderbird, the same about:config method applies.Affected if JIT is enabled (any of the jit-related options set to true). The vulnerability only affects environments where JIT compilation is active.
-
Confirm application is actively used with JIT code generationThis is implicit - if the browser or Thunderbird is used to visit websites or process content that triggers JavaScript execution, the JIT compiler generates code. The vulnerability occurs during JIT code invalidation while following an iterator, which happens during normal JavaScript execution in web content.Affected if The application has been used to browse websites or process content containing JavaScript, which triggers JIT code generation.
You are affected if you have Firefox below 111.0, Firefox ESR below 102.9, or Thunderbird below 102.9, and JIT compilation is enabled (the default state), and you use the browser to process JavaScript 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 · scoped102.9111.0
Upgrade to Firefox 111, Firefox ESR 102.9, or Thunderbird 102.9 or later to patch the JIT code invalidation vulnerability.
Firefox 111.0, Firefox ESR 102.9, Thunderbird 102.9
- 1. Back up any important data and bookmarks in your current Firefox, Firefox ESR, or Thunderbird installation
- 2. Close all instances of the affected application
- 3. Download the latest version from the official Mozilla website (www.mozilla.org) or use your system's package manager
- 4. For Firefox: Install version 111.0 or later
- 5. For Firefox ESR: Install version 102.9 or later
- 6. For Thunderbird: Install version 102.9 or later
- 7. Restart the application after installation
- 8. Verify the installed version by checking Help > About (Firefox/Thunderbird)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25751 — 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-2023-25751 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