FirefoxWeb browser · Mozilla
CVE-2022-22741
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 · uneditedWhen resizing a popup while requesting fullscreen access, the popup would have become unable to leave fullscreen mode. This vulnerability affects Firefox ESR < 91.5, Firefox < 96, and Thunderbird < 91.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 denial-of-service vulnerability in Firefox and Thunderbird where a popup window, when resized simultaneously while requesting fullscreen access, becomes locked in fullscreen mode and cannot exit, preventing user interaction with the browser UI.
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
< 96.0
Firefox EsrWeb browser
< 91.5< 91.5CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify the installed Mozilla productOpen the application and navigate to Help > About (Firefox) or Help > About Thunderbird. The product name (Firefox, Firefox ESR, or Thunderbird) will be displayed in the title bar of the About window.Affected if The product is Firefox, Firefox ESR, or Thunderbird
-
Determine the installed version numberIn the Help > About window, note the version number displayed (for example, 95.0.1 or 91.4.1).Affected if A version number is displayed
-
Compare version to affected rangesFor Firefox: check if version is below 96.0. For Firefox ESR: check if version is below 91.5. For Thunderbird: check if version is below 91.5.Affected if Firefox < 96.0, Firefox ESR < 91.5, or Thunderbird < 91.5
-
Verify fullscreen popup condition (optional confirmation)To confirm the specific trigger condition, open a website in a popup window, then simultaneously resize the window while clicking to request fullscreen mode. Observe if the fullscreen becomes locked and cannot be exited with Esc or other methods.Affected if The fullscreen mode becomes permanently locked after this action
A user is affected if they are running Firefox below 96.0, Firefox ESR below 91.5, or Thunderbird below 91.5, and may experience the fullscreen lock when resizing a popup window during fullscreen request.
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 · scoped91.596.0
Upgrade to Firefox ESR 91.5+, Firefox 96+, or Thunderbird 91.5+ to remediate this vulnerability.
Firefox 96.0, Firefox ESR 91.5, or Thunderbird 91.5
- Identify which Mozilla product you are using (Firefox, Firefox ESR, or Thunderbird)
- Open the application and navigate to Help > About [Product Name]
- Click 'Check for Updates' or allow the application to automatically check for updates
- Install the available update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22741 — 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-2022-22741 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