# CVE-2022-46874: Code injection in Firefox

> Attackers can execute malicious code by exploiting filename truncation that hides valid extensions, affecting Firefox and Thunderbird users.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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-46874, GHSA-pwwf-7f48-895h, MGASA-2022-0484, SUSE-SU-2022:4636-1, UBUNTU-CVE-2022-46874

## What is CVE-2022-46874?

CVE-2022-46874 is a high-severity code injection vulnerability in Mozilla Firefox, 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

A file with a long filename could have had its filename truncated to remove the valid extension, leaving a malicious extension in its place. This could potentially led to user confusion and the execution of malicious code.<br/>*Note*: This issue was originally included in the advisories for Thunderbird 102.6, but a patch (specific to Thunderbird) was omitted, resulting in it actually being fixed in Thunderbird 102.6.1. This vulnerability affects Firefox < 108, Thunderbird < 102.6.1, Thunderbird < 102.6, and Firefox ESR < 102.6.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `MozillaThunderbird` | SUSE:Linux Enterprise Module for Package Hub 15 SP4 | All versions | 102.6.1-150200.8.99.1 |
| `MozillaThunderbird` | SUSE:Linux Enterprise Workstation Extension 15 SP4 | All versions | 102.6.1-150200.8.99.1 |
| `MozillaThunderbird` | openSUSE:Leap 15.4 | All versions | 102.6.1-150200.8.99.1 |

Products: Mozilla Firefox, Mozilla Firefox Esr, Mozilla Thunderbird.

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

Upgrade to a fixed version.

## Is CVE-2022-46874 being exploited?

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

## Other vulnerabilities in Mozilla Firefox

- [CVE-2019-11708](https://insights.sbomify.com/CVE-2019-11708/): Mozilla Firefox and Thunderbird Sandbox Escape (critical 10.0, exploited in the wild)
- [CVE-2010-3765](https://insights.sbomify.com/CVE-2010-3765/): Mozilla Multiple Products Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2022-26486](https://insights.sbomify.com/CVE-2022-26486/): Mozilla Firefox Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2022-26485](https://insights.sbomify.com/CVE-2022-26485/): Mozilla Firefox Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2019-11707](https://insights.sbomify.com/CVE-2019-11707/): Mozilla Firefox and Thunderbird Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46874 is a high-severity code injection vulnerability in Mozilla Firefox, 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-46874 in the wild and no public exploit code.

Affected product: Mozilla Firefox. 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-46874/ (Markdown: https://insights.sbomify.com/CVE-2022-46874/index.md)
```

## Sources

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

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