Cloudanix VulnDB

CVE-2022-45419

Medium · 6.5

CVSS

6.5

EPSS

0.4%

Published

Dec 22, 2022

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A browser flaw let an encrypted connection stay open even after the user told it to stop trusting the other side's security certificate.

Exploitation
Requires User Interaction
Attacker needs
User Interaction
Complexity
Moderate
Impact
Data Tampering
Component
Application
Class
Cryptographic Weakness
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

The browser maintains an active TLS session established under a user-added certificate exception even after the exception is removed, allowing the connection to continue without re-validating the certificate.

Why it matters to the business

Organizations face continued exposure to untrusted remote servers through browser sessions, increasing risk of data integrity compromise on encrypted connections that should have been terminated.

How an attack unfolds

An attacker presents an invalid TLS certificate; the victim adds a security exception and establishes a long-lived connection; after the victim deletes the exception the browser keeps the session alive, treating the certificate as trusted for the duration of that connection.

How to fix it

Upgrade affected Firefox installations to version 107 or later; enforce automatic browser updates across the fleet and revoke any lingering manual certificate exceptions.

How to confirm the fix worked

Confirm Firefox version is 107 or newer on all endpoints; audit certificate exception lists and verify that connections to previously excepted hosts now enforce proper certificate validation.

Typical attack path

  1. Attacker hosts a service using an invalid TLS certificate
  2. Victim is tricked into adding a permanent security exception for that certificate
  3. Victim opens a TLS connection that remains active
  4. Victim removes the security exception
  5. Browser silently keeps the original connection alive without re-checking the certificate

How to detect it

Search browser history and certificate exception logs for additions and subsequent removals of exceptions followed by continued network activity to the same host; examine TLS session durations in proxy or endpoint logs for connections that outlive exception removal events.

What your security team should do

  • Prioritize deployment of Firefox 107+ across all managed systems
  • Disable or restrict manual certificate exception workflows where possible
  • Monitor browser update compliance metrics
  • Review logs for any long-lived connections to hosts that previously required exceptions

The record

If 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.

Affected packages

Ecosystem Package Introduced Fixed
Ubuntu:18.04:LTS firefox 0 107.0+build2-0ubuntu0.18.04.1
Ubuntu:18.04:LTS mozjs38 0 No fix
Ubuntu:18.04:LTS mozjs52 0 No fix
Ubuntu:20.04:LTS firefox 0 107.0+build2-0ubuntu0.20.04.1
Ubuntu:20.04:LTS mozjs52 0 No fix
Ubuntu:20.04:LTS mozjs68 0 No fix
Ubuntu:22.04:LTS mozjs78 0 No fix
Ubuntu:22.04:LTS mozjs91 0 No fix
Ubuntu:Pro:18.04:LTS mozjs38 0 No fix
Ubuntu:Pro:18.04:LTS mozjs52 0 No fix
Ubuntu:Pro:20.04:LTS mozjs52 0 No fix
Ubuntu:Pro:20.04:LTS mozjs68 0 No fix
Ubuntu:Pro:22.04:LTS mozjs78 0 No fix
openSUSE:Tumbleweed MozillaFirefox 0 107.0-1.1
openSUSE:Tumbleweed firefox-esr 0 128.5.1-1.1

Related vulnerabilities