dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-29944

HIGH · 8.4 CVSS v3.1 Published 2024-03-22
Fix available
A fix is available. Upgrade to 115.9.1 or later.
See remediation →
89/100
Remediation priority · High
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 attacker was able to inject an event handler into a privileged object that would allow arbitrary JavaScript execution in the parent process. Note: This vulnerability affects Desktop Firefox only, it does not affect mobile versions of Firefox. This vulnerability affects Firefox < 124.0.1 and Firefox ESR < 115.9.1.

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 JavaScript injection vulnerability in Desktop Firefox allows an attacker to inject an event handler into a privileged object, enabling arbitrary JavaScript execution in the parent process with elevated privileges. This bypasses normal sandboxing and affects Firefox < 124.0.1 and Firefox ESR < 115.9.1.

MitigationUpdate Firefox to version 124.0.1 or later and Firefox ESR to 115.9.1 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.9.1<= 124.0.1
Debian LinuxOperating system
Affected:= 10.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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Identify Firefox installation
    Open Firefox and navigate to about:support, or run 'firefox --version' from command line, or check your system's package manager for installed Firefox package version
    Affected if No Firefox installation is found or the application is not Firefox
  2. Determine exact Firefox version
    In about:support, locate the 'Version' field under 'Application'; from command line, the output of 'firefox --version' shows the version number (e.g., 124.0, 115.8, etc.)
    Affected if Unable to retrieve version information
  3. Compare against vulnerable version ranges
    Compare your installed version: for standard Firefox, any version below 124.0.1 is vulnerable; for Firefox ESR, any version below 115.9.1 is vulnerable
    Affected if Installed version is < 124.0.1 for standard Firefox OR < 115.9.1 for Firefox ESR
  4. Check for Debian package version (if applicable)
    If running Debian 10, use 'dpkg -l | grep firefox' or 'apt-cache policy firefox-esr' to check the installed Debian package version
    Affected if Running Debian 10 with an unpatched Firefox package

You are affected if your installed Firefox version is below 124.0.1 (regular) or below 115.9.1 (ESR), or if you are on Debian 10 with an unpatched Firefox package.

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.9.1 or later
Fixed in 115.9.1
Interim mitigation

Update Firefox to version 124.0.1 or later and Firefox ESR to 115.9.1 or later to remediate this vulnerability.

Recommended fix High confidence

Firefox 124.0.1 or Firefox ESR 115.9.1

  1. Open Firefox and navigate to Help > About Firefox (or go to about:support)
  2. Click "Check for Updates" or allow automatic updates to complete
  3. Restart Firefox after the update completes
  4. Verify the installed version by checking Help > About Firefox - it should show 124.0.1 or higher for Firefox, or 115.9.1 or higher for Firefox ESR
  5. Alternatively, download the latest Firefox or Firefox ESR directly from the official Mozilla website (www.mozilla.org) and reinstall

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-29944 — 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-29944 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