dbcve.org
FirefoxWeb browser · Mozilla

CVE-2024-2611

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 115.9.0 / 124.0 or later.
See remediation →
59/100
Remediation priority · Elevated
Public exploit Remotely reachable

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 missing delay on when pointer lock was used could have allowed a malicious page to trick a user into granting permissions. This vulnerability affects Firefox < 124, Firefox ESR < 115.9, and Thunderbird < 115.9.

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

A detailed technical summary for this CVE is being prepared.

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.0< 124.0
Debian LinuxOperating system
Affected:= 10.0
ThunderbirdApplication
Affected:< 115.9.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

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.0 / 124.0 or later
Fixed in 115.9.0124.0
Recommended fix High confidence

Firefox 124.0, Firefox ESR 115.9, or Thunderbird 115.9.0

  1. 1. Check your current Firefox or Thunderbird version by navigating to the application menu > Help > About [Application Name]
  2. 2. If using Firefox: Download Firefox 124.0 or later from the official Mozilla website (www.mozilla.org) or use your system's package manager to update
  3. 3. If using Firefox ESR: Update to Firefox ESR 115.9 or later through your organization's software distribution or package manager
  4. 4. If using Thunderbird: Download Thunderbird 115.9.0 or later from the official Mozilla website or update via package manager
  5. 5. After installation, restart the application to apply the update
  6. 6. Verify the update was successful by checking the version in Help > About
Caveat None expected; this is a routine security update with no known breaking changes

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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