dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-7652

HIGH · 7.5 CVSS v3.1 Published 2024-09-06
Fix available
A fix is available. Upgrade to 115.13.0 / 128.0 or later.
See remediation →
84/100
Remediation priority · High
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
An error in the ECMA-262 specification relating to Async Generators could have resulted in a type confusion, potentially leading to memory corruption and an exploitable crash. 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 type confusion vulnerability in Firefox's SpiderMonkey JavaScript engine exists due to an error in the ECMA-262 specification implementation for Async Generators. This flaw can lead to memory corruption and an exploitable crash, classified as HIGH severity with CVSS 7.5.

MitigationUpdate vulnerable applications to fixed versions: Firefox to 128+, Firefox ESR to 115.13+, or Thunderbird to 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.0< 128.0
ThunderbirdApplication
Affected:< 115.13.0>= 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Firefox version
    Open Firefox, click Help > About Firefox, or enter 'about:support' in the address bar. The version number is displayed at the top. Alternatively, check your system's program files or package manager listing for Firefox.
    Affected if Version is below 128.0 (including any version between 115.13.0 and 127.x)
  2. Identify installed Mozilla Thunderbird version
    Open Thunderbird, click Help > About Thunderbird. The version number is displayed. Alternatively, check your system's program files or package manager listing for Thunderbird.
    Affected if Version is below 115.13.0 OR version is 116.0 or higher but below 128.0
  3. Confirm SpiderMonkey engine is in use
    This vulnerability is in the SpiderMonkey JavaScript engine used by Firefox and Thunderbird. Both browsers have this engine enabled by default - no additional configuration needed to be vulnerable.
    Affected if The browser or Thunderbird is running and executing JavaScript (default behavior)
  4. Compare against affected version ranges
    Take the version number found in steps 1 or 2 and compare against: Firefox < 115.13.0, Firefox < 128.0, Thunderbird < 115.13.0, Thunderbird >= 116.0 and < 128.0. Any version below 128.0 for Firefox or the specified ranges for Thunderbird indicates potential exposure.
    Affected if Installed version falls within any of the vulnerable ranges listed

You are affected if you have Firefox below 128.0 or Thunderbird below 115.13.0 or between 116.0-127.x, as the type confusion in SpiderMonkey's Async Generator implementation can be triggered during normal JavaScript execution.

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.0 / 128.0 or later
Fixed in 115.13.0128.0
Interim mitigation

Update vulnerable applications to fixed versions: Firefox to 128+, Firefox ESR to 115.13+, or Thunderbird to 115.13+/128+ as appropriate.

Recommended fix High confidence

Firefox 128.0 / Firefox ESR 115.13 / Thunderbird 128.0 (depending on product and release channel)

  1. 1. Check the current installed version of Firefox or Thunderbird by navigating to the application's menu and selecting 'About Firefox' or 'About Thunderbird'
  2. 2. If using Firefox (non-ESR): Upgrade to version 128.0 or later
  3. 3. If using Firefox ESR: Upgrade to version 115.13 or later
  4. 4. If using Thunderbird (ESR or standard): Upgrade to version 128.0 or later
  5. 5. Restart the application after the update completes
  6. 6. Verify the update was successful by checking 'About' again to confirm the version number
Caveat Standard Mozilla release upgrade; no major breaking changes expected for typical users

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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