CVE-2024-11693
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 .library-ms files. *Note: This issue only affected Windows operating systems. Other operating systems are unaffected.* This vulnerability affects Firefox < 133, Firefox ESR < 128.5, Thunderbird < 133, and Thunderbird < 128.5.
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 downloading .library-ms files on Windows, bypassing a security safeguard that warns users about potentially dangerous file types.
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< 128.5.0< 133.0< 128.5.0>= 129.0, < 133.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
- 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.
-
Verify Windows operating systemCheck if the system is running Windows (this vulnerability only affects Windows platforms). You can check via system information or command: 'systeminfo' on Windows or review system properties.Affected if The system is not running Windows - this vulnerability does not affect other operating systems.
-
Identify installed Mozilla productDetermine if Mozilla Firefox or Thunderbird is installed. Check the application list, installed programs, or look for the executable in standard installation directories (typically C:\Program Files\Mozilla Firefox or C:\Program Files\Mozilla Thunderbird).Affected if Neither Firefox nor Thunderbird is installed - the vulnerability only applies to these products.
-
Check Firefox versionOpen Firefox and navigate to Menu > Help > About Firefox, or enter 'about:support' in the address bar. Alternatively, check the version property of the firefox.exe file in the installation directory.Affected if The installed Firefox version is below 128.5.0 or is any version from 129.0 through 132.x (versions below 133.0 that are not 128.5.0).
-
Check Thunderbird versionOpen Thunderbird and navigate to Menu > Help > About Thunderbird, or check the version property of the thunderbird.exe file in the installation directory.Affected if The installed Thunderbird version is below 128.5.0 or is any version from 129.0 through 132.x (versions below 133.0 that are not 128.5.0).
A user is affected if they are running Firefox or Thunderbird on Windows with a version that falls below 128.5.0 or between 129.0 and 132.x, and they download or handle .library-ms files.
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 · scoped128.5.0133.0
Update to Firefox 133, Firefox ESR 128.5, Thunderbird 133, or Thunderbird 128.5. Until updated, avoid opening .library-ms files downloaded from untrusted sources.
Firefox 133.0+ / Firefox ESR 128.5.0+ / Thunderbird 133.0+ / Thunderbird 128.5.0+
- 1. Open Firefox or Thunderbird and navigate to the Help menu
- 2. Select 'About Firefox' or 'About Thunderbird' to check the current version
- 3. If the version is below 133.0 (or below 128.5.0 for ESR/Thunderbird), click to download and install the update
- 4. Alternatively, download the latest version from the official Mozilla website: https://www.mozilla.org/
- 5. Restart the application after the update completes
- 6. Verify the version now shows 133.0 or later, or 128.5.0 or later for ESR
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11693 — 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-11693 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