CVE-2024-0745

What it actually does

Stack buffer overflow in the WebAudio OscillatorNode implementation that can corrupt adjacent stack memory and lead to a crash or arbitrary code execution.

Why it matters to the business

Users of affected browser versions may experience sudden crashes or, in successful attacks, loss of control over their systems when visiting malicious websites, increasing risk of data theft or further compromise across the organization.

How an attack unfolds

An attacker hosts a malicious webpage that instantiates an OscillatorNode with crafted parameters; when the page is loaded in an unpatched browser the node triggers the stack overflow, allowing the attacker to redirect execution flow.

How to fix it

Upgrade Mozilla Firefox to version 122 or later; ensure automatic updates are enabled and verify the installed version after patching.

How to confirm the fix worked

Confirm the browser reports version 122 or higher; test rendering of known OscillatorNode test cases and monitor for crashes in audio processing paths.

Typical attack path

1. Attacker prepares a webpage containing malicious WebAudio OscillatorNode usage
2. Victim is lured to the page via phishing or compromised site
3. Browser renders the page and processes the audio node
4. Stack buffer overflows and attacker-controlled data is written to the stack
5. Execution is redirected to attacker payload resulting in crash or code execution

How to detect it

Review browser crash logs and telemetry for entries involving OscillatorNode or WebAudio stack overflows; correlate with web request logs to malicious domains.

What your security team should do

• Immediately deploy Firefox 122+ across all managed endpoints
• Disable WebAudio features via enterprise policy if immediate update is not feasible
• Monitor browser crash reports for audio-related stack overflows
• Include the vulnerability in the next patch cycle and verify update compliance