CVE-2023-25732

What it actually does

Incorrect calculation of input size when encoding data from an inputStream in xpcom results in an out-of-bounds memory write, enabling memory corruption.

Why it matters to the business

Potential remote code execution or application crashes impacting users of widely deployed browsers and email clients, increasing operational risk until patched.

How an attack unfolds

An attacker supplies specially crafted content that reaches the vulnerable xpcom encoding path, causing the size miscalculation and subsequent out-of-bounds write that can be leveraged for arbitrary code execution.

How to fix it

Upgrade Mozilla Firefox to version 110 or later, Firefox ESR to 102.8 or later, and Thunderbird to 102.8 or later.

How to confirm the fix worked

Confirm installed versions meet or exceed the fixed releases listed above; test rendering of encoded streams for absence of crashes or corruption.

Typical attack path

1. Deliver malicious webpage or email attachment to target
2. Trigger inputStream data encoding in xpcom
3. Exploit resulting out-of-bounds write to corrupt memory and achieve code execution

How to detect it

Review application crash logs for memory corruption signatures in xpcom encoding paths; correlate with access to untrusted content sources.

What your security team should do

• Apply updates to all affected Mozilla products immediately
• Prioritize patching for users handling untrusted web or email content
• Monitor vendor advisories for any subsequent backports or additional fixes