dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-10468

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-29
Fix available
A fix is available. Upgrade to 132.0 or later.
See remediation →
60/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
Potential race conditions in IndexedDB could have caused memory corruption, leading to a potentially exploitable crash. This vulnerability affects Firefox < 132 and Thunderbird < 132.

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 · moderate confidence

Race conditions in IndexedDB (the browser's client-side storage API) allow concurrent operations to interfere with each other, causing memory corruption that can lead to crashes. This is a multi-threaded synchronization issue in Firefox and Thunderbird's IndexedDB implementation.

MitigationUpgrade to Firefox 132 or Thunderbird 132 or later to receive the patch addressing these race conditions.

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:< 132.0
ThunderbirdApplication
Affected:< 132.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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 installed Mozilla product
    Check if Firefox or Thunderbird is installed on the system by looking for the application in the system launcher, program files, or running 'firefox --version' or 'thunderbird --version' in a terminal
    Affected if Either Firefox or Thunderbird is installed
  2. Determine Firefox version
    Open Firefox, click Help > About Firefox, or run 'firefox --version' in a terminal to obtain the exact version number
    Affected if Version is displayed as less than 132.0 (for example, 131.x or earlier)
  3. Determine Thunderbird version
    Open Thunderbird, click Help > About Thunderbird, or run 'thunderbird --version' in a terminal to obtain the exact version number
    Affected if Version is displayed as less than 132.0 (for example, 131.x or earlier)
  4. Verify IndexedDB usage context
    Recall whether you or any applications running in the browser use IndexedDB for client-side storage (commonly used by webmail, productivity web apps, and offline-capable websites)
    Affected if IndexedDB is actively used by any web applications in the browser

You are affected if you use Firefox or Thunderbird with a version number lower than 132.0 and your browser applications utilize IndexedDB functionality.

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 132.0 or later
Fixed in 132.0
Interim mitigation

Upgrade to Firefox 132 or Thunderbird 132 or later to receive the patch addressing these race conditions.

Recommended fix High confidence

Firefox 132.0 and Thunderbird 132.0

  1. Check the current version of Firefox or Thunderbird by navigating to Help > About (or using the menu)
  2. Download Firefox 132.0 or later from the official Mozilla website (www.mozilla.org)
  3. Download Thunderbird 132.0 or later from the official Mozilla website (www.mozilla.org)
  4. Install the updated version, ensuring to close the application before installation
  5. Restart the browser or email client after installation completes
  6. Verify the installation by checking Help > About to confirm the version is 132.0 or later
Caveat Standard minor version upgrade with no expected breaking changes; as with any browser update, verify that critical extensions and saved data function normally

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10468 — 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-2024-10468 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