dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-5700

HIGH · 7.0 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 115.12 / 127.0 or later.
See remediation →
73/100
Remediation priority · Elevated
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
Memory safety bugs present in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Firefox < 127, Firefox ESR < 115.12, and Thunderbird < 115.12.

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

Memory safety bugs in Firefox 126, Firefox ESR 115.11, and Thunderbird 115.11 showed evidence of memory corruption. With sufficient effort, these vulnerabilities could potentially be exploited to run arbitrary code.

MitigationUpgrade to Firefox 127 or later, Firefox ESR 115.12 or later, or Thunderbird 115.12 or later 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:< 115.12< 127.0
ThunderbirdApplication
Affected:< 115.12

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
Local
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/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. Identify installed Mozilla product
    Check if Firefox or Thunderbird is installed by looking for the application in your system. On Windows, check Program Files or Program Files (x86). On macOS, check /Applications. On Linux, check /usr/bin or use package manager.
    Affected if Either Firefox or Thunderbird is installed
  2. Determine Firefox version
    Open Firefox, click the menu (three horizontal lines), go to Help > About Firefox. The version number is displayed in the window that opens.
    Affected if Firefox version is less than 115.12 OR less than 127.0 (note: 127.0 and above are not affected)
  3. Determine Thunderbird version
    Open Thunderbird, click the menu (three horizontal lines), go to Help > About Thunderbird. The version number is displayed in the window that opens.
    Affected if Thunderbird version is less than 115.12

You are affected if either Firefox version is below 115.12 (ESR branch) or below 127.0 (main branch), or Thunderbird version is below 115.12.

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.12 / 127.0 or later
Fixed in 115.12127.0
Interim mitigation

Upgrade to Firefox 127 or later, Firefox ESR 115.12 or later, or Thunderbird 115.12 or later to remediate this vulnerability.

Recommended fix High confidence

Firefox 127 (stable), Firefox ESR 115.12+, or Thunderbird 115.12+

  1. Back up your current browser profile and any critical data
  2. Close all running instances of Firefox or Thunderbird
  3. Download the latest Firefox release from https://www.mozilla.org/firefox/download/ or Firefox ESR from https://www.mozilla.org/firefox/enterprise/
  4. Download the latest Thunderbird from https://www.thunderbird.net/
  5. Install the new version by running the downloaded installer
  6. After installation, verify the version by navigating to Help > About Firefox or Help > About Thunderbird
  7. Ensure the installed version is Firefox >= 127, Firefox ESR >= 115.12, or Thunderbird >= 115.12
Caveat Minor: Some legacy add-ons may not be compatible with newer versions; verify add-on compatibility before upgrading

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $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 $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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