dbcve.org
FirefoxWeb browser · Mozilla

CVE-2023-4046

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-01
Fix available
A fix is available. Upgrade to 102.14 / 115.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
In some circumstances, a stale value could have been used for a global variable in WASM JIT analysis. This resulted in incorrect compilation and a potentially exploitable crash in the content process. This vulnerability affects Firefox < 116, Firefox ESR < 102.14, and Firefox ESR < 115.1.

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 confidence

This is a vulnerability in Firefox's WebAssembly JIT compiler where a stale (outdated) value could be used for a global variable during JIT analysis, resulting in incorrect compiled code and potentially exploitable crashes in the content process.

MitigationUpdate Firefox to version 116 or later, or apply the relevant ESR patches (102.14 or 115.1) to remediate this vulnerability.

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
Affected:< 116.0>= 102.0, < 102.14>= 115.0, < 115.1
Debian LinuxOperating system
Affected:= 11.0= 12.0

CVSS 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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Firefox browser version
    Open Firefox, go to Menu > Help > About Firefox, or navigate to about:support to see the version number
    Affected if The version is less than 102.14, or between 102.14 and 115.0 (inclusive of 115.0), or less than 116.0 but greater than or equal to 115.1 (i.e., affected ranges are < 102.14, >= 102.0 to < 115.1, and >= 115.0 to < 116.0)
  2. Verify WebAssembly JIT compiler is enabled
    In Firefox address bar, navigate to about:config and search for javascript.options.wasm_jit. Check if the boolean value is set to true
    Affected if javascript.options.wasm_jit is set to true (JIT is enabled)
  3. Check for additional JIT-related flags
    In about:config, search for wasm and review related JIT flags such as javascript.options.wasm_baselinejit and javascript.options.wasm_optimizing_jit
    Affected if Any WebAssembly JIT-related options are set to true (the vulnerability exists in the JIT compilation path)
  4. Confirm running architecture and OS version (if on Debian Linux)
    Run 'cat /etc/debian_version' in terminal, or check OS details via 'uname -a'
    Affected if Running Debian 11.0 or 12.0 with an affected Firefox version from system packages

User is affected if running an affected Firefox version (less than 102.14, or 115.0 to less than 115.1, or less than 116.0) AND WebAssembly JIT compilation is enabled in the browser configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 102.14 / 115.1 / 116.0 or later
Fixed in 102.14115.1116.0
Interim mitigation

Update Firefox to version 116 or later, or apply the relevant ESR patches (102.14 or 115.1) to remediate this vulnerability.

Recommended fix High confidence

Firefox 116.0, Firefox ESR 102.14, Firefox ESR 115.1 (or later)

  1. Identify the current Firefox version (Help > About Firefox)
  2. For Firefox 115.x users: upgrade to Firefox 115.1 or later
  3. For Firefox ESR 102.x users: upgrade to Firefox ESR 102.14 or later
  4. For Firefox 115 ESR users: upgrade to Firefox ESR 115.1 or later
  5. For Firefox users on versions < 115: upgrade to Firefox 116.0 or later
  6. On Debian systems, run 'apt update && apt upgrade' to apply security updates containing the fixed Firefox packages
  7. Restart Firefox after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4046 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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