FirefoxWeb browser · Mozilla
CVE-2022-34468
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 · uneditedAn iframe that was not permitted to run scripts could do so if the user clicked on a <code>javascript:</code> link. This vulnerability affects Firefox < 102, Firefox ESR < 91.11, Thunderbird < 102, and Thunderbird < 91.11.
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 cross-origin security bypass in Firefox and Thunderbird allows an iframe with script restrictions to execute JavaScript code when a user clicks on a javascript: link. This violates the intended Same-Origin Policy security boundary and allows script execution in contexts where it should be blocked.
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
< 102.0
Firefox EsrWeb browser
< 91.11< 91.11CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify installed Firefox versionOpen Firefox, click the menu button (three lines), select Help, then About Firefox. The version number is displayed on the page that opens. Alternatively, run 'firefox --version' in a terminal.Affected if version shown is below 102.0 (for standard Firefox) or below 91.11 (for Firefox ESR)
-
Identify installed Thunderbird versionOpen Thunderbird, click the menu button (three lines), select Help, then About Thunderbird. The version number is displayed on the page that opens. Alternatively, run 'thunderbird --version' in a terminal.Affected if version shown is below 91.11
-
Confirm Firefox release channelIn Firefox, navigate to 'about:support' in the address bar and look for the 'Application Update' section or 'Build Configuration' to determine if you are running the standard release or Extended Support Release (ESR).Affected if running Firefox ESR below version 91.11, or standard Firefox below version 102.0
You are affected if you are running any version of Mozilla Firefox below 102.0, Firefox ESR below 91.11, or Thunderbird below 91.11.
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.11102.0
Update affected browsers (Firefox to version 102+, Firefox ESR to 91.11+, Thunderbird to version 102+ or 91.11+) to remediate this vulnerability.
Firefox 102.0, Firefox ESR 91.11, Thunderbird 91.11 or 102.0
- Update Firefox to version 102.0 or later
- Update Firefox ESR to version 91.11 or later
- Update Thunderbird to version 91.11 or later (or version 102.0 for the rapid release)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34468 — 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-34468 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