FirefoxWeb browser · Mozilla

CVE-2024-6602

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 115.13 / 128.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A mismatch between allocator and deallocator could have led to memory corruption. This vulnerability affects Firefox < 128, Firefox ESR < 115.13, Thunderbird < 115.13, and Thunderbird < 128.

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 memory management vulnerability exists where memory allocated using one method is deallocated using a mismatched deallocator, leading to heap corruption. This type of allocator/deallocator mismatch can cause undefined behavior and potentially enable arbitrary code execution.

MitigationUpdate affected Mozilla products to the patched versions: Firefox 128, Firefox ESR 115.13, or Thunderbird 115.13/128 as appropriate.

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:< 115.13< 128.0
ThunderbirdApplication
Affected:< 115.13>= 116.0, < 128.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Check if Firefox is installed
    On Windows, look for 'Mozilla Firefox' in Program Files or check Add/Remove Programs. On Linux, run 'which firefox' or 'dpkg -l | grep firefox'. On macOS, check /Applications for Firefox.app.
    Affected if Firefox is installed on the system
  2. Determine Firefox version
    Open Firefox, go to Menu > Help > About Firefox, or navigate to about:support in the address bar. Note the version number shown (e.g., 127.0.1, 115.12).
    Affected if Version is less than 115.13 or less than 128.0 (any version before 128.0 is affected)
  3. Check if Thunderbird is installed
    On Windows, look for 'Mozilla Thunderbird' in Program Files or check Add/Remove Programs. On Linux, run 'which thunderbird' or 'dpkg -l | grep thunderbird'. On macOS, check /Applications for Thunderbird.app.
    Affected if Thunderbird is installed on the system
  4. Determine Thunderbird version
    Open Thunderbird, go to Menu > Help > About Thunderbird. Note the version number shown.
    Affected if Version is less than 115.13, or version is 116.0 or higher but less than 128.0

If Firefox version is below 128.0, or Thunderbird version is below 115.13 or is between 116.0 and 127.x, the environment is affected by CVE-2024-6602.

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 115.13 / 128.0 or later
Fixed in 115.13128.0
Interim mitigation

Update affected Mozilla products to the patched versions: Firefox 128, Firefox ESR 115.13, or Thunderbird 115.13/128 as appropriate.

Recommended fix High confidence

Firefox 128.0 / Firefox ESR 115.13 / Thunderbird 128.0 / Thunderbird ESR 115.13

  1. Upgrade Firefox to version 128.0 or later
  2. Upgrade Firefox ESR to version 115.13 or later
  3. Upgrade Thunderbird to version 128.0 or later
  4. Upgrade Thunderbird ESR to version 115.13 or later

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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