FirefoxWeb browser · Mozilla
CVE-2022-29914
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 reusing existing popups Firefox would have allowed them to cover the fullscreen notification UI, which could have enabled browser spoofing attacks. This vulnerability affects Thunderbird < 91.9, Firefox ESR < 91.9, and Firefox < 100.
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 confidenceFirefox had a UI spoofing vulnerability where reusing existing popups could allow them to overlay and cover the fullscreen notification UI. This could enable attackers to display deceptive content by tricking users into believing they're seeing legitimate browser notifications.
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
< 100.0
Firefox EsrWeb browser
< 91.9< 91.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox versionOpen Firefox, navigate to Help > About Firefox, or run 'firefox --version' in terminalAffected if Version is less than 100.0 (regular Firefox)
-
Check Firefox ESR versionOpen Firefox ESR, navigate to Help > About Firefox, or run 'firefox --version' in terminalAffected if Version is less than 91.9 (Firefox ESR)
-
Check Thunderbird versionOpen Thunderbird, navigate to Help > About Thunderbird, or run 'thunderbird --version' in terminalAffected if Version is less than 91.9 (Thunderbird)
If the installed Firefox version is below 100.0, or Firefox ESR/Thunderbird is below 91.9, the UI spoofing vulnerability allowing popups to cover fullscreen notifications is present.
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.9100.0
Upgrade to Firefox >= 100, Firefox ESR >= 91.9, or Thunderbird >= 91.9. The fix ensures popups cannot cover the fullscreen notification UI.
Firefox 100.0, Firefox ESR 91.9, Thunderbird 91.9
- Check current Firefox/Thunderbird version by navigating to Help > About [Application Name]
- Download the latest Firefox 100.0 or later from https://www.mozilla.org/firefox/
- Download the latest Firefox ESR 91.9 or later from https://www.mozilla.org/firefox/enterprise/
- Download the latest Thunderbird 91.9 or later from https://www.thunderbird.net/
- Alternatively, use the built-in update mechanism: Help > Check for Updates
- Restart the application after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29914 — 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-29914 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