FirefoxWeb browser · Mozilla

CVE-2023-4575

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-11
Fix available
A fix is available. Upgrade to 102.15 / 115.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
When creating a callback over IPC for showing the File Picker window, multiple of the same callbacks could have been created at a time and eventually all simultaneously destroyed as soon as one of the callbacks finished. This could have led to a use-after-free causing a potentially exploitable crash. This vulnerability affects Firefox < 117, Firefox ESR < 102.15, Firefox ESR < 115.2, Thunderbird < 102.15, and Thunderbird < 115.2.

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

A use-after-free vulnerability in Firefox and Thunderbird where IPC callbacks for the File Picker window could be created multiple times simultaneously, and all would be destroyed when any single callback completed, leading to a dangling pointer and potentially exploitable crash.

MitigationUpgrade to Firefox 117 or later, Firefox ESR 102.15/115.2 or later, or Thunderbird 102.15/115.2 or later to patch the callback lifecycle management issue.

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:< 117.0>= 115.0, < 115.2
Firefox EsrWeb browser
Affected:< 102.15
ThunderbirdApplication
Affected:< 115.2

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
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 checks

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

  1. Identify the installed Mozilla product
    Open the application and go to Help > About (Firefox or Thunderbird) to display the version number, or run: firefox --version or thunderbird --version
    Affected if The installed product is Mozilla Firefox or Mozilla Thunderbird
  2. Check Firefox version against affected ranges
    If running Firefox, compare your installed version to: < 117.0, or >= 115.0 and < 115.2
    Affected if Firefox version is 115.0, 115.1, or any version below 115.2 (but >= 115.0) or below 117.0
  3. Check Firefox ESR version against affected ranges
    If running Firefox ESR, compare your installed version to: < 102.15
    Affected if Firefox ESR version is 102.14 or lower
  4. Check Thunderbird version against affected ranges
    If running Thunderbird, compare your installed version to: < 115.2
    Affected if Thunderbird version is 115.1 or lower (including 102.x versions below 102.15)

You are affected if running any Firefox version 115.0-115.1, any Firefox version below 117.0, any Firefox ESR below 102.15, or any Thunderbird below 115.2.

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.15 / 115.2 / 117.0 or later
Fixed in 102.15115.2117.0
Interim mitigation

Upgrade to Firefox 117 or later, Firefox ESR 102.15/115.2 or later, or Thunderbird 102.15/115.2 or later to patch the callback lifecycle management issue.

Recommended fix High confidence

Firefox 117.0, Firefox ESR 102.15/115.2, Thunderbird 102.15/115.2

  1. Upgrade Firefox to version 117.0 or later
  2. If using Firefox ESR 102.x, upgrade to version 102.15 or later
  3. If using Firefox ESR 115.x, upgrade to version 115.2 or later
  4. If using Thunderbird 102.x, upgrade to version 102.15 or later
  5. If using Thunderbird 115.x, upgrade to version 115.2 or later

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

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4575 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4575 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