CVE-2024-0754

What it actually does

Certain WebAssembly source files trigger a crash when inspected in developer tools, resulting in denial of service for the affected process.

Why it matters to the business

Developers experience unexpected browser crashes during routine inspection of web content, interrupting debugging workflows and potentially delaying software development and testing activities.

How an attack unfolds

An attacker prepares a specially crafted WebAssembly source file and hosts it on a web page. A victim using an affected browser version opens the developer tools and loads the file for inspection, causing an immediate crash.

How to fix it

Upgrade Mozilla Firefox to version 122 or later. Apply updates promptly across all managed endpoints and verify that developer tools are no longer exposed to untrusted WebAssembly sources until patched.

How to confirm the fix worked

Confirm the installed Firefox version is 122 or higher; attempt to load known triggering WebAssembly files in developer tools on a test system and verify absence of crashes.

Typical attack path

1. Craft a malicious WebAssembly source file that triggers the crash condition
2. Host the file on a publicly accessible web page
3. Social engineer or otherwise induce a target user to visit the page and open developer tools to inspect the file

How to detect it

Review browser crash logs and telemetry for sudden terminations while developer tools are active; correlate with access to WebAssembly-containing pages.

What your security team should do

• Prioritize deployment of Firefox 122+ to all developer workstations and browsers within the environment
• Educate developers on avoiding inspection of untrusted WebAssembly content until updates are applied
• Monitor for browser crash reports correlated with developer tools usage