Cloudanix VulnDB

CVE-2024-0744

High · 7.5

CVSS

7.5

EPSS

0.6%

Published

Jan 23, 2024

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A problem in older versions of the Firefox browser could let a website cause the program to crash and potentially allow an attacker to take control of the user's computer.

Exploitation
Remote Unauthenticated
Attacker needs
None
Complexity
Low
Impact
Denial Of Service
Component
Application
Class
Memory Corruption
Remediation
Upgrade
Effort
Low
Patch risk
Low

What it actually does

JIT-compiled code in the browser engine dereferences an invalid pointer value, resulting in memory corruption that manifests as an exploitable crash.

Why it matters to the business

Users running affected Firefox versions may experience unexpected browser crashes when visiting malicious sites, disrupting productivity and potentially allowing attackers to execute arbitrary code on the endpoint.

How an attack unfolds

An attacker hosts a specially crafted webpage that triggers just-in-time compilation paths containing the wild pointer dereference; when the victim loads the page in an unpatched Firefox instance, the corruption occurs and the attacker attempts to turn the resulting crash into code execution.

How to fix it

Upgrade Mozilla Firefox to version 122 or later on all endpoints. Enforce automatic updates where possible and verify the installed version after deployment.

How to confirm the fix worked

Confirm that all Firefox installations report version 122 or higher via about:support or enterprise management tools; test that previously triggering pages no longer cause crashes.

Typical attack path

  1. Attacker prepares and hosts a malicious webpage designed to exercise JIT compilation
  2. Victim visits the page with an affected Firefox version
  3. JIT engine generates code that dereferences an invalid pointer
  4. Memory corruption triggers an exploitable crash state
  5. Attacker attempts to leverage the corruption for code execution or further exploitation

How to detect it

Review Firefox crash reports and telemetry for unexpected JIT-related crashes; examine web proxy or endpoint logs for visits to suspicious domains around the time of any browser instability.

What your security team should do

  • Immediately deploy Firefox 122 or newer across the organization
  • Monitor for any remaining instances of Firefox versions below 122
  • Review browser crash reports for patterns consistent with memory corruption
  • Consider temporary browser sandboxing or content filtering as a compensating control until updates are complete

The record

In some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could have led to an exploitable crash. This vulnerability affects Firefox < 122.

Affected packages

Ecosystem Package Introduced Fixed
Ubuntu:18.04:LTS mozjs38 0 No fix
Ubuntu:18.04:LTS mozjs52 0 No fix
Ubuntu:20.04:LTS firefox 0 122.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 mozjs102 0 No fix
Ubuntu:22.04:LTS mozjs78 0 No fix
Ubuntu:22.04:LTS mozjs91 0 No fix
Ubuntu:24.04:LTS mozjs102 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
Ubuntu:Pro:24.04:LTS mozjs102 0 No fix
openSUSE:Tumbleweed MozillaFirefox 0 122.0-1.1
openSUSE:Tumbleweed firefox-esr 0 128.5.1-1.1

Related vulnerabilities