CVE-2023-32214
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 · uneditedProtocol handlers `ms-cxh` and `ms-cxh-full` could have been leveraged to trigger a denial of service. *Note: This attack only affects Windows. Other operating systems are not affected.* This vulnerability affects Firefox < 113, Firefox ESR < 102.11, and Thunderbird < 102.11.
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 · moderate confidenceThe ms-cxh and ms-cxh-full protocol handlers in Firefox, Firefox ESR, and Thunderbird for Windows can be triggered to cause a denial of service condition. This appears to be a local DoS vulnerability where the protocol handlers can be invoked (likely through a crafted URI or web page) to cause the application to become unresponsive or crash.
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< 113.0< 102.11< 102.11CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 installations). Open Command Prompt and run: systeminfo | findstr /B /C:"OS Name"Affected if The system is NOT running Windows - the vulnerability only affects Windows versions of Firefox, Firefox ESR, and Thunderbird
-
Check Firefox versionIf Firefox is installed, open Firefox, go to Help > About Firefox, or navigate to about:support. Alternatively, check the program files directory for the version. Compare the displayed version number against 113.0Affected if The installed Firefox version is lower than 113.0 on Windows
-
Check Firefox ESR versionIf Firefox ESR is installed, open the application, go to Help > About Firefox ESR, or navigate to about:support. Compare the displayed version number against 102.11Affected if The installed Firefox ESR version is lower than 102.11 on Windows
-
Check Thunderbird versionIf Thunderbird is installed, open the application, go to Help > About Thunderbird. Compare the displayed version number against 102.11Affected if The installed Thunderbird version is lower than 102.11 on Windows
A user is affected if they are running Firefox below 113.0, Firefox ESR below 102.11, or Thunderbird below 102.11 on a Windows system, as these versions contain the vulnerable ms-cxh and ms-cxh-full protocol handlers.
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 · scoped102.11113.0
Update affected Windows installations to Firefox 113 or later, Firefox ESR 102.11 or later, or Thunderbird 102.11 or later. No other mitigation is required beyond applying the vendor patch.
Firefox 113.0, Firefox ESR 102.11, or Thunderbird 102.11 (or later)
- Verify current version by opening Firefox/Thunderbird and navigating to Help > About (or checking application settings)
- Update to the fixed version: Firefox 113.0 or later, Firefox ESR 102.11 or later, or Thunderbird 102.11 or later
- For enterprise/deployment environments, use the appropriate software distribution channel (e.g., Windows Update, enterprise patch management, or download from mozilla.org
- Restart the application after update to ensure the fix is applied
- Verify the updated version by checking Help > About to confirm the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32214 — 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-2023-32214 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