dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-45421

HIGH · 8.8 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.5 / 107.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Mozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in Thunderbird 102.4. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Firefox ESR < 102.5, Thunderbird < 102.5, and Firefox < 107.

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

Memory safety bugs in Thunderbird 102.4 and Firefox with evidence of memory corruption, potentially exploitable for arbitrary code execution via the browser rendering engine or JavaScript engine.

MitigationUpdate to Thunderbird 102.5+, Firefox ESR 102.5+, or Firefox 107+ to apply the memory safety patches.

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:< 107.0
Firefox EsrWeb browser
Affected:< 102.5
ThunderbirdApplication
Affected:< 102.5

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
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 checks

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

  1. Identify installed Mozilla product
    Check if Firefox or Thunderbird is installed. On Windows, look in Program Files for 'Mozilla Firefox' or 'Mozilla Thunderbird'. On Linux, check package manager: dpkg -l | grep -i firefox or rpm -qa | grep -i thunderbird. On macOS, check /Applications for Firefox.app or Thunderbird.app.
    Affected if Neither Firefox nor Thunderbird is installed (not affected)
  2. Determine Firefox version
    For Firefox: Open menu > Help > About Firefox, or navigate to about:support in address bar, or run 'firefox --version' from command line.
    Affected if Version is less than 107.0 (for regular Firefox) or less than 102.5 (for Firefox ESR)
  3. Determine Thunderbird version
    For Thunderbird: Open menu > Help > About Thunderbird, or navigate to about:support in address bar, or run 'thunderbird --version' from command line.
    Affected if Version is less than 102.5
  4. Confirm Firefox ESR variant
    If Firefox is installed, check if it is the ESR variant by opening about:support and looking for 'Firefox Extended Support Release' or checking the version string for 'esr' notation.
    Affected if Firefox ESR version is less than 102.5

You are affected if you have Firefox version < 107.0 (regular) or < 102.5 (ESR), or Thunderbird version < 102.5 installed.

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.5 / 107.0 or later
Fixed in 102.5107.0
Interim mitigation

Update to Thunderbird 102.5+, Firefox ESR 102.5+, or Firefox 107+ to apply the memory safety patches.

Recommended fix High confidence

Firefox 107.0, Firefox ESR 102.5, or Thunderbird 102.5

  1. Navigate to the official Mozilla download page at www.mozilla.org for your respective product (Firefox, Firefox ESR, or Thunderbird)
  2. Download the latest version of your installed Mozilla product
  3. Close all instances of the browser or email client
  4. Run the installer to complete the upgrade
  5. Alternatively, open the application and go to Help > About to trigger automatic update check and installation
Caveat Mozilla stable releases typically do not introduce breaking changes for end users

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-45421 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-45421 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