CVE-2024-6600

What it actually does

Out-of-bounds memory access triggered when GLSL shaders allocate more than 8192 integers in private shader memory on macOS because Angle allocation checks are too permissive.

Why it matters to the business

Risk of browser or email client crashes and potential code execution on macOS endpoints, which can lead to data exposure, service disruption, and require emergency patching across user populations.

How an attack unfolds

An attacker supplies a crafted webpage or email containing a malicious GLSL shader; when the browser compiles and allocates shader memory, the lenient check allows overflow past the 8192-int boundary, resulting in out-of-bounds access that an attacker can leverage for memory corruption or control-flow hijacking.

How to fix it

Upgrade Firefox to 128 or newer, Firefox ESR to 115.13 or newer, and Thunderbird to 115.13 or newer on macOS systems.

How to confirm the fix worked

Verify installed browser and email-client versions meet or exceed the fixed releases; inspect macOS crash logs for Angle/GLSL shader allocation failures prior to the update.

Typical attack path

1. Serve malicious web content or email attachment to target
2. Trigger GLSL shader compilation and large private-memory allocation
3. Bypass allocation limit checks to cause out-of-bounds read/write
4. Corrupt adjacent memory structures to achieve code execution or denial of service

How to detect it

Review browser process crash reports and Angle/GLSL shader logs on macOS for allocation-size anomalies or out-of-bounds faults; correlate with web or email activity preceding the crash.

What your security team should do

• Immediately deploy the listed version updates to all macOS endpoints
• Prioritize macOS user populations given the platform-specific shader flaw
• Monitor browser crash telemetry for shader-related faults until patching completes