# CVE-2022-45414: Server-side request forgery in Thunderbird

> Attackers can force Thunderbird to make remote network requests via HTML tags, bypassing remote content blocking and potentially leaking user information.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-45414, GHSA-gvhr-fq94-q7h9, MGASA-2022-0452, SUSE-SU-2022:4334-1, UBUNTU-CVE-2022-45414, openSUSE-SU-2024:12544-1

## What is CVE-2022-45414?

CVE-2022-45414 is a high-severity server-side request forgery vulnerability in Mozilla Thunderbird, published on 22 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-45414?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `MozillaThunderbird` | SUSE:Linux Enterprise Module for Package Hub 15 SP3 | All versions | 102.5.1-150200.8.93.1 |
| `MozillaThunderbird` | SUSE:Linux Enterprise Module for Package Hub 15 SP4 | All versions | 102.5.1-150200.8.93.1 |
| `MozillaThunderbird` | SUSE:Linux Enterprise Workstation Extension 15 SP3 | All versions | 102.5.1-150200.8.93.1 |
| `MozillaThunderbird` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 102.5.1-150200.8.93.1 |
| `MozillaThunderbird` | openSUSE:Leap 15.3 | All versions | 102.5.1-150200.8.93.1 |
| `MozillaThunderbird` | openSUSE:Leap 15.4 | All versions | 102.5.1-150200.8.93.1 |
| `MozillaThunderbird` | openSUSE:Tumbleweed | All versions | 102.5.1-1.1 |

Products: Mozilla Thunderbird.

## How do I fix CVE-2022-45414?

Upgrade to a fixed version.

## Is CVE-2022-45414 being exploited?

There is no known exploitation of CVE-2022-45414 in the wild and no public exploit code.

## Other vulnerabilities in Mozilla Thunderbird

- [CVE-2026-92238](https://insights.sbomify.com/CVE-2026-92238/): Ambiguous parsing of mail headers (critical 9.8)
- [CVE-2026-84637](https://insights.sbomify.com/CVE-2026-84637/): Calendar invitation attachments could launch local executables (critical 9.8)
- [CVE-2021-43529](https://insights.sbomify.com/CVE-2021-43529/): Memory corruption in Thunderbird (critical 9.8)
- [CVE-2019-11703](https://insights.sbomify.com/CVE-2019-11703/): Memory corruption in Thunderbird (critical 9.8)
- [CVE-2019-11704](https://insights.sbomify.com/CVE-2019-11704/): Memory corruption in Thunderbird (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45414 and fix it if it is affected.

What it is: CVE-2022-45414 is a high-severity server-side request forgery vulnerability in Mozilla Thunderbird, published on 22 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-45414 in the wild and no public exploit code.

Affected product: Mozilla Thunderbird. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-45414/ (Markdown: https://insights.sbomify.com/CVE-2022-45414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-45414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-45414
- OSV: https://osv.dev/vulnerability/CVE-2022-45414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-45414/
Summaries are generated and may contain mistakes; the official description above is the record.