CVE-2023-7024

8.8 HIGH

📋 TL;DR

This vulnerability is a heap buffer overflow in WebRTC within Google Chrome that allows remote attackers to potentially exploit heap corruption via a crafted HTML page. Attackers could execute arbitrary code or cause denial of service. All users running vulnerable versions of Chrome are affected.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: Prior to 120.0.6099.129
Operating Systems: Windows, Linux, macOS, ChromeOS
Default Config Vulnerable: ⚠️ Yes
Notes: All default Chrome configurations are vulnerable. WebRTC is enabled by default.

📦 What is this software?

Chrome by Google

Google Chrome is the world's most popular web browser, used by over 3 billion users globally across Windows, macOS, Linux, Android, and iOS platforms. As a Chromium-based browser developed by Google, Chrome dominates the browser market with approximately 65% market share, making it a critical compon...

Learn more about Chrome →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, data theft, or ransomware deployment.

🟠

Likely Case

Browser crash/denial of service, potential information disclosure, or limited code execution within browser sandbox.

🟢

If Mitigated

Browser crash with no further impact if sandboxing holds, though sandbox escape is possible with heap corruption.

🌐 Internet-Facing: HIGH - Exploitable via visiting malicious websites, no authentication required.
🏢 Internal Only: MEDIUM - Requires user interaction (visiting malicious page), but internal phishing could exploit it.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Heap corruption vulnerabilities require careful exploitation but WebRTC is a complex attack surface. No public exploit available as of advisory dates.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 120.0.6099.129 and later

Vendor Advisory: https://chromereleases.googleblog.com/2023/12/stable-channel-update-for-desktop_20.html

Restart Required: Yes

Instructions:

1. Open Chrome. 2. Click three-dot menu → Help → About Google Chrome. 3. Chrome will automatically check for updates and install version 120.0.6099.129 or later. 4. Click 'Relaunch' to restart Chrome.

🔧 Temporary Workarounds

Disable WebRTC

all

Disables WebRTC functionality which removes the vulnerable component but breaks video/audio calling features.

chrome://flags/#disable-webrtc
Set 'WebRTC' flag to 'Disabled'

Use browser extensions to block WebRTC

all

Install extensions like 'WebRTC Leak Prevent' or 'uBlock Origin' with WebRTC blocking enabled.

🧯 If You Can't Patch

  • Deploy network filtering to block malicious websites and phishing attempts.
  • Implement application control to restrict browser usage to patched versions only.

🔍 How to Verify

Check if Vulnerable:

Check Chrome version: If version is less than 120.0.6099.129, system is vulnerable.

Check Version:

On Chrome: chrome://version/ or 'google-chrome --version' on Linux command line

Verify Fix Applied:

Confirm Chrome version is 120.0.6099.129 or higher after update.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash logs with WebRTC-related stack traces
  • Unexpected Chrome process termination events

Network Indicators:

  • Unusual WebRTC STUN/TURN traffic patterns
  • Requests to known malicious domains hosting exploit code

SIEM Query:

source="chrome_crash_logs" AND (process="chrome" OR process="chromium") AND message="*WebRTC*" AND message="*heap*"

🔗 References

📤 Share & Export