CVE-2022-31742
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 attacker could have exploited a timing attack by sending a large number of allowCredential entries and detecting the difference between invalid key handles and cross-origin key handles. This could have led to cross-origin account linking in violation of WebAuthn goals. This vulnerability affects Thunderbird < 91.10, Firefox < 101, and Firefox ESR < 91.10.
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 timing side-channel in Firefox and Thunderbird's WebAuthn implementation allows attackers to distinguish between invalid key handles and cross-origin key handles by measuring response times when sending large numbers of allowCredential entries. This enables cross-origin account linking that violates WebAuthn's isolation guarantees.
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< 101< 91.10< 91.10CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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, go to Menu > Help > About Firefox, or navigate to about:support. Locate the version number in the page that opens.Affected if The version shown is less than 101 (for example, 100.0, 98.0, etc.)
-
Check Firefox ESR versionOpen Firefox ESR, go to Menu > Help > About Firefox ESR, or navigate to about:support. Locate the version number in the page that opens.Affected if The version shown is less than 91.10 (for example, 91.9, 91.0, etc.)
-
Check Thunderbird versionOpen Thunderbird, go to Menu > Help > About Thunderbird. Locate the version number in the window that opens.Affected if The version shown is less than 91.10 (for example, 91.9, 78.x, etc.)
You are affected if any installed Firefox version is below 101, or any Firefox ESR or Thunderbird version is below 91.10, and the browser or mail client is used with WebAuthn-based authentication.
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.10101
Update affected products to patched versions: Thunderbird >= 91.10, Firefox >= 101, or Firefox ESR >= 91.10.
Firefox 101 or later; Firefox ESR 91.10 or later; Thunderbird 91.10 or later
- Determine your current Firefox, Firefox ESR, or Thunderbird version by navigating to the application menu and selecting 'Help' > 'About [Application]'
- If your version is below 101 (Firefox) or below 91.10 (Firefox ESR or Thunderbird), initiate an update
- For Firefox/Firefox ESR: Go to Menu > Help > About Firefox/About Firefox ESR and click 'Check for Updates' to download and install the latest version
- For Thunderbird: Go to Menu > Help > About Thunderbird and click 'Check for Updates' to download and install the latest version
- Alternatively, download the latest version directly from the official Mozilla website (www.mozilla.org) for your operating system
- Restart the application after the update completes
- Verify the update was successful by checking the version number again in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31742 — 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-31742 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