FirefoxWeb browser · Mozilla

CVE-2022-40957

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.3 / 105.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
Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<br>*This bug only affects Firefox on ARM64 platforms.*. This vulnerability affects Firefox ESR < 102.3, Thunderbird < 102.3, and Firefox < 105.

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

A cache coherence vulnerability exists in Firefox and Thunderbird on ARM64 platforms where instruction and data caches can become inconsistent during WebAssembly code generation. This inconsistency can cause the processor to execute corrupted instructions, leading to a potentially exploitable crash.

MitigationUpgrade Firefox to version 105 or later, or Firefox ESR/Thunderbird to version 102.3 or later on all ARM64 systems.

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:< 105.0
Firefox EsrWeb browser
Affected:< 102.3
ThunderbirdApplication
Affected:< 102.3

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
None
Availability
High

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

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

  1. Identify your system architecture
    Run 'uname -m' or 'dpkg --print-architecture' on Linux, or check System Information on macOS/Windows to confirm the processor is ARM64 (also shown as aarch64).
    Affected if The system is NOT ARM64 (x86_64/x64 systems are not affected by this CVE)
  2. Check installed Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line.
    Affected if The version number is less than 105.0 (for example, 104.x, 103.x, etc.)
  3. Check installed Firefox ESR version
    Open Firefox ESR, go to Help > About Firefox, or run 'firefox-esr --version' from command line.
    Affected if The ESR version is less than 102.3 (for example, 102.2, 102.1, 101.x, etc.)
  4. Check installed Thunderbird version
    Open Thunderbird, go to Help > About Thunderbird, or run 'thunderbird --version' from command line.
    Affected if The version number is less than 102.3 (for example, 102.2, 102.1, etc.)

You are affected only if running Firefox < 105.0, Firefox ESR < 102.3, or Thunderbird < 102.3 on an ARM64 (aarch64) system.

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.3 / 105.0 or later
Fixed in 102.3105.0
Interim mitigation

Upgrade Firefox to version 105 or later, or Firefox ESR/Thunderbird to version 102.3 or later on all ARM64 systems.

Recommended fix High confidence

Firefox 105.0+, Firefox ESR 102.3+, Thunderbird 102.3+

  1. Check current installed version: In Firefox, go to Help > About Firefox. In Thunderbird, go to Help > About Thunderbird.
  2. For Firefox: Download and install Firefox 105.0 or later from the official Mozilla website (www.mozilla.org).
  3. For Firefox ESR: Download and install Firefox ESR 102.3 or later from the official Mozilla website.
  4. For Thunderbird: Download and install Thunderbird 102.3 or later from the official Mozilla website.
  5. Restart the application after the update completes.
  6. Verify the update was successful by checking the version again in Help > About.
Caveat No breaking changes expected; this is a routine security update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40957 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