CVE-2022-36319
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 combining CSS properties for overflow and transform, the mouse cursor could interact with different coordinates than displayed. This vulnerability affects Firefox ESR < 102.1, Firefox ESR < 91.12, Firefox < 103, Thunderbird < 102.1, and Thunderbird < 91.12.
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 clickjacking vulnerability in Firefox and Thunderbird where combining CSS overflow and transform properties causes the mouse cursor to interact with different coordinates than what is visually displayed. This allows attackers to potentially trick users into clicking unintended elements.
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< 103.0< 102.1< 91.12< 102.1< 91.12CVSS 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 installed Mozilla productCheck if Firefox or Thunderbird is installed. On Windows, look in Program Files or Program Files (x86). On macOS, check /Applications. On Linux, check package manager or /usr/lib/firefox or /usr/lib/thunderbird.Affected if Either Firefox or Thunderbird is installed
-
Determine Firefox versionOpen Firefox, go to Help > About Firefox (or navigate to about:support). Note the version number displayed.Affected if Firefox version is less than 103.0 (regular) or less than 102.1/91.12 (ESR)
-
Determine Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird (or navigate to about:support). Note the version number displayed.Affected if Thunderbird version is less than 102.1 or less than 91.12
-
Check Firefox ESR branchIf using Firefox ESR, confirm the exact ESR version (102.x series or 91.x series) from the about:support page.Affected if Firefox ESR is version 102.0.x or lower, or 91.x below 91.12
The environment is affected if Firefox (any channel below 103.0) or Thunderbird (below 102.1 or 91.12) is installed and used to interact with web content containing the problematic CSS overflow+transform combination.
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.12102.1103.0
Update affected Firefox ESR to 102.1+, Firefox to 103+, or Thunderbird to 102.1+. For web applications, avoid problematic overflow+transform combinations or implement click-jacking defenses like X-Frame-Options CSP.
Firefox 103.0, Firefox ESR 102.1 or 91.12, Thunderbird 102.1 or 91.12
- Upgrade Firefox to version 103.0 or later
- Upgrade Firefox ESR to version 102.1 or later (or 91.12 if on the 91.x ESR branch)
- Upgrade Thunderbird to version 102.1 or later (or 91.12 if on the 91.x branch)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36319 — 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-36319 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