CVE-2024-1059

8.8 HIGH

📋 TL;DR

This vulnerability is a use-after-free flaw in Google Chrome's Peer Connection component, allowing remote attackers to potentially exploit stack corruption via a crafted HTML page. It affects users of Google Chrome versions prior to 121.0.6167.139, putting them at risk of arbitrary code execution or browser crashes when visiting malicious websites.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: Versions prior to 121.0.6167.139
Operating Systems: Windows, macOS, Linux, Android, iOS
Default Config Vulnerable: ⚠️ Yes
Notes: All default configurations of affected Chrome versions are vulnerable; no special settings are required for exploitation.

📦 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 full system compromise, data theft, or malware installation on the victim's device.

🟠

Likely Case

Browser crash (denial of service) or limited code execution within the browser sandbox, potentially enabling further attacks.

🟢

If Mitigated

Minimal impact if patched promptly; otherwise, risk is reduced by security controls like sandboxing, but exploitation remains possible.

🌐 Internet-Facing: HIGH, as exploitation can occur via visiting a malicious website, making it easily accessible to remote attackers.
🏢 Internal Only: MEDIUM, as internal users could be targeted via phishing or compromised internal sites, but requires user interaction.

🎯 Exploit Status

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

Exploitation requires user interaction (e.g., visiting a malicious page) and may involve bypassing Chrome's sandbox, but no public proof-of-concept is known at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 121.0.6167.139

Vendor Advisory: https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_30.html

Restart Required: Yes

Instructions:

1. Open Google Chrome. 2. Click the three-dot menu > Help > About Google Chrome. 3. Chrome will automatically check for updates and prompt to restart if an update is available. 4. Restart Chrome to apply the patch.

🔧 Temporary Workarounds

Disable WebRTC or Peer Connections

all

Temporarily disable WebRTC features to mitigate the vulnerability, but this may break functionality for video calls or real-time communication.

chrome://flags/#disable-webrtc (set to Disabled)
chrome://flags/#enable-webrtc-hide-local-ips-with-mdns (set to Enabled)

🧯 If You Can't Patch

  • Restrict access to untrusted websites using web filtering or browser extensions to block malicious content.
  • Implement application whitelisting to prevent unauthorized execution of Chrome or related processes.

🔍 How to Verify

Check if Vulnerable:

Open Chrome, go to chrome://version, and check if the version is earlier than 121.0.6167.139.

Check Version:

On command line: google-chrome --version (Linux) or "C:\Program Files\Google\Chrome\Application\chrome.exe" --version (Windows)

Verify Fix Applied:

After updating, confirm the version in chrome://version is 121.0.6167.139 or later.

📡 Detection & Monitoring

Log Indicators:

  • Look for Chrome crash reports or error logs indicating memory corruption or use-after-free events in peer connection processes.

Network Indicators:

  • Monitor for unusual outbound connections from Chrome processes post-visit to suspicious domains, potentially indicating exploit payload delivery.

SIEM Query:

Example: event_source="Chrome" AND (event_description CONTAINS "crash" OR event_description CONTAINS "memory corruption")

🔗 References

📤 Share & Export