ThunderbirdApplication · Mozilla

CVE-2022-45414

HIGH · 8.1 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.5.1 or later.
See remediation →
88/100
Remediation priority · High
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
If a Thunderbird user quoted from an HTML email, for example by replying to the email, and the email contained either a VIDEO tag with the POSTER attribute or an OBJECT tag with a DATA attribute, a network request to the referenced remote URL was performed, regardless of a configuration to block remote content. An image loaded from the POSTER attribute was shown in the composer window. These issues could have given an attacker additional capabilities when targetting releases that did not yet have a fix for CVE-2022-3033 which was reported around three months ago. This vulnerability affects Thunderbird < 102.5.1.

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

Thunderbird fails to honor the remote content blocking setting when processing quoted HTML emails containing VIDEO tags with POSTER attributes or OBJECT tags with DATA attributes. This allows arbitrary network requests to remote URLs and displays referenced images in the composer window, bypassing user-configured content restrictions.

MitigationUpgrade Thunderbird to version 102.5.1 or later. Until then, avoid quoting or replying to emails from untrusted sources that contain VIDEO or OBJECT tags.

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
ThunderbirdApplication
Affected:< 102.5.1

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
None

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

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

  1. Check Thunderbird version
    Open Thunderbird and go to Help > About Thunderbird, or run 'thunderbird --version' from command line
    Affected if Version displayed is lower than 102.5.1 (e.g., 102.5.0, 102.4.x, earlier releases)
  2. Verify the remote content blocking setting
    Go to Edit > Preferences > Privacy & Security and locate the 'Remote Content' section - note that this setting exists but is bypassed by the vulnerability
    Affected if Remote content blocking is enabled (the bug bypasses this protection regardless of its state)

If Thunderbird version is below 102.5.1, the remote content blocking setting can be bypassed by VIDEO or OBJECT tags in quoted HTML emails, allowing unauthorized network requests.

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.1 or later
Fixed in 102.5.1
Interim mitigation

Upgrade Thunderbird to version 102.5.1 or later. Until then, avoid quoting or replying to emails from untrusted sources that contain VIDEO or OBJECT tags.

Recommended fix High confidence

Thunderbird 102.5.1

  1. 1. Check current Thunderbird version: Go to Help > About Thunderbird or run `thunderbird --version` in terminal
  2. 2. Back up Thunderbird profile data (optional but recommended): Find profile folder via Help > Troubleshooting Information > Profile Folder
  3. 3. Download Thunderbird 102.5.1 or later from https://www.thunderbird.net/
  4. 4. Install the Thunderbird upgrade by running the downloaded installer
  5. 5. After installation, verify the version via Help > About Thunderbird shows version 102.5.1 or higher
Caveat Minor: Some legacy add-ons may not be compatible with Thunderbird 102.x; review add-on compatibility after upgrade

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

Fix this in Thunderbird Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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