dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-45404

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.5 / 107.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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
Through a series of popup and <code>window.print()</code> calls, an attacker can cause a window to go fullscreen without the user seeing the notification prompt, resulting in potential user confusion or spoofing attacks. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107.

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

This is a UI spoofing vulnerability where attackers bypass the fullscreen notification prompt through a sequence of popup windows and window.print() calls, causing the browser to enter fullscreen mode without visible user warning. This can lead to user confusion or spoofing attacks where malicious content appears to be a legitimate fullscreen application.

MitigationUpdate affected applications to Firefox ESR 102.5, Thunderbird 102.5, or Firefox 107 or later to patch the fullscreen notification bypass.

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:< 107.0
Firefox EsrWeb browser
Affected:< 102.5
ThunderbirdApplication
Affected:< 102.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Mozilla Firefox version
    Navigate to Firefox menu > Help > About Firefox, or enter 'about:support' in the address bar, or run 'firefox --version' from command line
    Affected if The version displayed is below 107.0 (for example, 106.x or earlier)
  2. Check Mozilla Firefox ESR version
    Navigate to Firefox menu > Help > About Firefox, or enter 'about:support' in the address bar, or run 'firefox-esr --version' from command line
    Affected if The version displayed is below 102.5 (for example, 102.4.x or earlier)
  3. Check Mozilla Thunderbird version
    Navigate to Thunderbird menu > Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if The version displayed is below 102.5 (for example, 102.4.x or earlier)
  4. Verify JavaScript is enabled in the browser
    In Firefox: Address bar > type 'about:config' > search for 'javascript.enabled' - ensure it is set to true; In Thunderbird: Go to Edit > Preferences > Privacy & Security > scroll to Permissions > check 'Enable JavaScript'
    Affected if JavaScript is enabled - this is required for the exploit to function

You are affected if you run any version of Firefox below 107.0, Firefox ESR below 102.5, or Thunderbird below 102.5, with JavaScript enabled in the browser settings.

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 102.5 / 107.0 or later
Fixed in 102.5107.0
Interim mitigation

Update affected applications to Firefox ESR 102.5, Thunderbird 102.5, or Firefox 107 or later to patch the fullscreen notification bypass.

Recommended fix High confidence

Firefox 107.0, Firefox ESR 102.5, Thunderbird 102.5

  1. Check current Firefox version by navigating to menu > Help > About Firefox (or for Thunderbird: menu > Help > About Thunderbird)
  2. For Firefox: Download and install Firefox 107.0 from the official Mozilla website (www.mozilla.org)
  3. For Firefox ESR: Download and install Firefox ESR 102.5 from the official Mozilla website
  4. For Thunderbird: Download and install Thunderbird 102.5 from the official Mozilla website
  5. Restart the application after installation to complete the 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
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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