FirefoxWeb browser · Mozilla
CVE-2022-45415
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 · uneditedWhen downloading an HTML file, if the title of the page was formatted as a filename with a malicious extension, Firefox may have saved the file with that extension, leading to possible system compromise if the downloaded file was later ran. This vulnerability affects 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 confidenceFirefox fails to sanitize page titles when saving HTML files, allowing attackers to embed malicious file extensions (e.g., .exe, .js, .bat) in the page title. When users download such HTML pages, Firefox saves the file with the malicious extension instead of .html, potentially leading to arbitrary code execution if the user opens the file.
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
< 107.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox version numberOpen Firefox, click the menu button (three horizontal lines), select Help, then select About Firefox. The version number is displayed in the window that opens.Affected if The displayed version is lower than 107.0 (for example, 106.0, 106.0.1, 104.0, etc.)
-
Verify version via command line (Windows)Run the command: wmic datafile where "name='C:\\Program Files\\Mozilla Firefox\\firefox.exe'" get VersionAffected if The reported version is less than 107.0
-
Verify version via command line (macOS)Run the command: /Applications/Firefox.app/Contents/MacOS/firefox --versionAffected if The reported version is less than 107.0
-
Verify version via command line (Linux)Run the command: firefox --versionAffected if The reported version is less than 107.0
If Firefox version is below 107.0, the environment is vulnerable to the page title sanitization flaw during HTML file saves.
Generated from the published advisory. Verify against your own configuration.
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 · scoped107.0
Upgrade Firefox to version 107 or later, which properly handles filename sanitization during downloads.
Firefox 107.0
- Open Firefox and navigate to Help > About Firefox (or enter 'about:support' in the address bar)
- Check if the current version is below 107.0
- If below 107.0, click 'Check for Updates' or allow automatic update to complete
- Restart Firefox after the update completes
- Verify the version is now 107.0 or later by returning to About Firefox
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
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 locallyCheck whether your project pulls in CVE-2022-45415 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45415 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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