CVE-2023-29531

What it actually does

Out-of-bounds memory access via WebGL APIs on macOS resulting in memory corruption and potential exploitable crash in affected browser processes.

Why it matters to the business

Mac users of the browser and email client face elevated risk of remote compromise or denial of service until updates are applied, increasing support burden and potential data exposure for organizations with macOS fleets.

How an attack unfolds

An attacker hosts malicious content that invokes WebGL APIs in a crafted sequence; when rendered by the vulnerable macOS build the API call triggers an out-of-bounds read/write, corrupting memory and allowing subsequent control-flow hijacking or crash.

How to fix it

Upgrade Firefox to version 112 or later, Firefox ESR to 102.10 or later, and Thunderbird to 102.10 or later on all macOS systems; disable WebGL via about:config (webgl.disabled=true) as a temporary mitigation where patching is delayed.

How to confirm the fix worked

Verify installed versions match or exceed the fixed releases; confirm WebGL is disabled or test rendering of known trigger content in an isolated environment to ensure the crash vector is closed.

Typical attack path

1. Deliver malicious webpage or email attachment containing WebGL content
2. Victim renders the content in an affected macOS Firefox or Thunderbird instance
3. WebGL API triggers out-of-bounds memory access
4. Memory corruption occurs enabling code execution or denial of service

How to detect it

Review browser crash logs for WebGL-related faults on macOS systems; correlate with web proxy or mail logs showing visits to untrusted domains shortly before crashes.

What your security team should do

• Immediately prioritize macOS endpoint inventory and push the listed updates
• Apply temporary WebGL disablement for high-risk macOS populations
• Monitor vendor advisories for any follow-on patches or additional affected products