FirefoxWeb browser · Mozilla
CVE-2022-45419
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 · uneditedIf the user added a security exception for an invalid TLS certificate, opened an ongoing TLS connection with a server that used that certificate, and then deleted the exception, Firefox would have kept the connection alive, making it seem like the certificate was still trusted. 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 confidenceWhen a user adds a security exception for an invalid TLS certificate, opens an active connection using that certificate, then deletes the exception, Firefox fails to invalidate the existing connection. This causes the browser to continue displaying the connection as trusted even though the user explicitly revoked trust in the certificate.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 versionOpen about:firefox in the address bar or go to Menu > Help > About Firefox. Look for the version number displayed.Affected if The version shown is less than 107.0 (for example, 106.0, 106.0.1, etc.)
-
Identify active TLS connectionsOpen about:networking in the address bar and examine the active connections listed under the 'sockets' and 'http2' tabs. Each entry shows the host and connection state.Affected if Any active connections exist to hosts where a security exception was previously added but has since been removed from the exception list.
-
Verify exception list is empty but connection persistsGo to about:preferences#privacy, scroll to 'Certificates', click 'View Exceptions', and confirm the list is empty. Then check if any of the hosts from step 2 are still accessible via HTTPS without certificate errors.Affected if The exception list is empty but an active HTTPS connection to a previously excepted host remains established and displays as trusted.
-
Check certificate validation statusClick the lock icon in the address bar for an active connection, inspect the certificate, and compare it against the current exception list in about:preferences#privacy under 'View Exceptions'.Affected if The certificate being used by an active connection does not appear in the exceptions list but the connection still shows as secure without errors.
A user is affected if running Firefox version below 107.0 AND has an active connection that was established under a now-deleted security exception, with the connection still appearing trusted.
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 to Firefox 107 or later. Users who cannot upgrade immediately should restart Firefox to clear any connections established under now-removed security exceptions.
Firefox 107.0
- 1. Check current Firefox version by clicking Help > About Firefox
- 2. Download Firefox 107.0 or later from the official Mozilla website (www.mozilla.org)
- 3. Install the updated Firefox version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45419 — 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-45419 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