CVE-2024-0743

What it actually does

An unchecked return value in TLS handshake code can trigger a denial-of-service crash in the browser's networking layer.

Why it matters to the business

Unexpected browser or email client crashes during secure connections can interrupt user workflows, reduce availability of web and email services, and increase support overhead for organizations relying on these applications.

How an attack unfolds

An attacker acts as a malicious TLS server or performs a man-in-the-middle position on a connection and returns a handshake response that exercises the unchecked return value path, causing the client process to terminate.

How to fix it

Upgrade Mozilla Firefox to 122 or later, Firefox ESR to 115.9 or later, and Thunderbird to 115.9 or later. Apply updates through the product's built-in mechanism or enterprise deployment channels as soon as available.

How to confirm the fix worked

Confirm the installed product versions meet or exceed the fixed releases listed above; perform functional TLS connection tests from the updated clients and review release notes for the specific fix.

Typical attack path

1. Position as a TLS endpoint reachable by the victim client
2. Initiate or intercept a TLS handshake
3. Return crafted handshake data that triggers the unchecked return value
4. Observe or induce client process crash

How to detect it

Review browser and system crash logs for entries referencing TLS handshake routines or networking code around the time of unexpected process termination; correlate with network logs showing connections to untrusted TLS endpoints.

What your security team should do

• Prioritize deployment of the fixed versions across all managed endpoints
• Enable automatic updates where policy permits
• Monitor crash-reporting telemetry for TLS-related terminations until patching is complete