CVE-2023-37201

What it actually does

Use-after-free condition triggered when creating a WebRTC connection over HTTPS, resulting in memory corruption that can lead to arbitrary code execution.

Why it matters to the business

Attackers could gain full control of affected systems, leading to data theft, system compromise, or ransomware deployment; high ecosystem prevalence increases exposure risk across many deployments.

How an attack unfolds

An attacker hosts a malicious HTTPS site that initiates a WebRTC connection; when the victim visits, the use-after-free is triggered allowing code execution in the browser process.

How to fix it

Upgrade affected products to fixed versions including redisson/redisson (GIT) at commit fe6a2571801656ff1599ef87bdee20f519a5d1fe or later; apply browser updates to Firefox 115+, Firefox ESR 102.13+, and Thunderbird 102.13+.

How to confirm the fix worked

Verify installed versions against the fixed commits or release numbers; test WebRTC functionality post-update to confirm no crashes on connection setup.

Typical attack path

1. Attacker prepares malicious HTTPS webpage with WebRTC initiation code
2. Victim is lured to visit the page
3. WebRTC connection setup begins
4. Use-after-free condition is triggered for memory corruption and payload execution

How to detect it

Review browser process crash logs and memory dumps for use-after-free patterns during WebRTC sessions; check web server access logs for unexpected HTTPS referrers initiating WebRTC.

What your security team should do

• Prioritize patching all instances to the specified fixed commits within 48 hours given high CVSS
• Monitor for any new exploit maturity signals
• Block untrusted WebRTC origins via policy where feasible