CVE-2024-3863
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 · uneditedThe executable file warning was not presented when downloading .xrm-ms files. *Note: This issue only affected Windows operating systems. Other operating systems are unaffected.* This vulnerability affects Firefox < 125, Firefox ESR < 115.10, and Thunderbird < 115.10.
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 and Thunderbird failed to display the executable file warning when users downloaded .xrm-ms files on Windows systems. This allowed potentially malicious executable files to be downloaded without user warning, as .xrm-ms files (Windows Credential Manager related) were not recognized as executables requiring a warning prompt.
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< 115.10.0< 125.0< 115.10CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Identify installed Mozilla productCheck if Firefox or Thunderbird is installed. On Windows, look in Program Files or Program Files (x86) for Mozilla Firefox or Mozilla Thunderbird folders. Alternatively, check the Windows registry under HKLM\SOFTWARE\Mozilla\Mozilla Firefox or HKLM\SOFTWARE\Mozilla\Thunderbird for the installed version.Affected if Neither Firefox nor Thunderbird is installed - the CVE does not apply.
-
Check Firefox version on WindowsOpen Firefox, go to Help > About Firefox, or navigate to about:support in the address bar. The version number is displayed at the top. Alternatively, check the file properties of firefox.exe in the installation directory.Affected if Firefox version is less than 115.10.0 or less than 125.0 on a Windows system.
-
Check Thunderbird version on WindowsOpen Thunderbird, go to Help > About Thunderbird, or navigate to about:support in the address bar. The version number is displayed at the top. Alternatively, check the file properties of thunderbird.exe in the installation directory.Affected if Thunderbird version is less than 115.10 on a Windows system.
-
Confirm operating system is WindowsCheck the system OS by running 'winver' from the Run dialog, or checking System Properties. This vulnerability only affects Windows systems.Affected if Running a non-Windows operating system - the CVE does not apply.
A user is affected if they have Firefox versions below 115.10.0 or below 125.0, or Thunderbird below 115.10, and are running on Windows.
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 · scoped115.10115.10.0125.0
Update Firefox to version 125 or later, Firefox ESR to 115.10 or later, and Thunderbird to 115.10 or later to receive the executable warning for .xrm-ms file downloads. Until patched, avoid downloading .xrm-ms files from untrusted sources.
Firefox 125.0 (or later), Firefox ESR 115.10 (or later), Thunderbird 115.10 (or later)
- 1. Open Firefox or Thunderbird and navigate to Help > About Firefox/Thunderbird to check the current version
- 2. If the version is below 125.0 for Firefox, below 115.10 for Firefox ESR, or below 115.10 for Thunderbird, an update is required
- 3. Download the latest version from the official Mozilla website: https://www.mozilla.org/
- 4. Close all browser/application windows before installing
- 5. Run the installer and follow the prompts to complete the update
- 6. After installation, verify the version by checking Help > About again to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3863 — 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-2024-3863 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