FirefoxWeb browser · Mozilla
CVE-2024-11698
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 · uneditedA flaw in handling fullscreen transitions may have inadvertently caused the application to become stuck in fullscreen mode when a modal dialog was opened during the transition. This issue left users unable to exit fullscreen mode using standard actions like pressing "Esc" or accessing right-click menus, resulting in a disrupted browsing experience until the browser is restarted. *This bug only affects the application when running on macOS. Other operating systems are unaffected.* This vulnerability affects Firefox < 133, Firefox ESR < 128.5, Thunderbird < 133, and Thunderbird < 128.5.
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 confidenceA logic flaw in Firefox and Thunderbird on macOS causes the browser to become permanently stuck in fullscreen mode when a modal dialog is opened during a fullscreen transition. The application fails to properly exit fullscreen state, disabling standard exit methods like pressing Escape or using right-click menus, forcing users to restart the browser.
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
< 128.5.0< 133.0< 128.5.0>= 129.0, < 133.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if running macOSVerify the operating system is macOS. This vulnerability only affects macOS environments. If running Linux or Windows, the system is not affected by this specific flaw.Affected if The system is not running macOS (the vulnerability only affects macOS builds of Firefox and Thunderbird)
-
Check Firefox versionOpen Firefox, go to Help > About Firefox, or navigate to about:support in the address bar. Note the version number displayed.Affected if The installed Firefox version is less than 133.0 (specifically < 128.5.0 or between 128.5.0 and 132.x)
-
Check Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird. Note the version number displayed.Affected if The installed Thunderbird version is less than 128.5.0 OR between 129.0 and 132.x (less than 133.0)
-
Identify if fullscreen was active during modal dialogDetermine if a modal dialog (such as a save dialog, print dialog, or authentication prompt) was opened while transitioning into or out of fullscreen mode. Check if Escape key or right-click menu options fail to exit fullscreen.Affected if The browser is currently stuck in fullscreen mode with no ability to exit using standard methods, and this occurred after a modal dialog was shown during a fullscreen transition
The environment is affected if running Firefox < 133.0 or Thunderbird < 128.5.0 (or 129.0 <= version < 133.0) on macOS, and the browser is stuck in fullscreen mode after a modal dialog appeared during a fullscreen transition.
Generated from the published advisory. Verify against your own configuration.
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 · scoped128.5.0133.0
Upgrade to Firefox 133, Firefox ESR 128.5, Thunderbird 133, or Thunderbird 128.5 on macOS systems to resolve the fullscreen transition handling defect.
Firefox 133.0 (stable) / Firefox ESR 128.5.0 / Thunderbird 133.0 or 128.5.0
- Upgrade Firefox to version 133.0 or later for the stable release, or Firefox ESR to version 128.5.0 or later
- Upgrade Thunderbird to version 133.0 or later, or version 128.5.0 or later
- After upgrading, restart the application to ensure the fix is fully applied
- Verify fullscreen functionality works correctly by testing modal dialog interactions during fullscreen transitions
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
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 locallyCheck whether your project pulls in CVE-2024-11698 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11698 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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