CVE-2024-3168

8.8 HIGH

📋 TL;DR

This CVE describes a use-after-free vulnerability in Chrome's DevTools that could allow a remote attacker to exploit heap corruption via a crafted HTML page. Attackers could potentially execute arbitrary code or cause browser crashes. All users running vulnerable Chrome versions are affected.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: Prior to 122.0.6261.57
Operating Systems: Windows, macOS, Linux, ChromeOS
Default Config Vulnerable: ⚠️ Yes
Notes: Requires DevTools functionality to be accessible, which 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 full system compromise, data theft, or malware installation.

🟠

Likely Case

Browser crash, denial of service, or limited information disclosure.

🟢

If Mitigated

No impact if Chrome is updated to patched version or DevTools is disabled.

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

🎯 Exploit Status

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

Requires user to visit malicious webpage. No public exploit code known at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 122.0.6261.57 and later

Vendor Advisory: https://chromereleases.googleblog.com/2024/02/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 and install updates. 4. Click 'Relaunch' to restart Chrome.

🔧 Temporary Workarounds

Disable DevTools

all

Prevent exploitation by disabling Chrome DevTools access

chrome://flags/#enable-devtools-experiments → Disabled
chrome://flags/#enable-devtools-experiments → Disabled

Use Chrome Enterprise policies

windows

Disable DevTools via group policy for enterprise deployments

Set 'DeveloperToolsAvailability' policy to 2 (Disallow use)

🧯 If You Can't Patch

  • Restrict web browsing to trusted sites only
  • Implement application whitelisting to prevent unauthorized Chrome execution

🔍 How to Verify

Check if Vulnerable:

Check Chrome version in About Google Chrome page. If version is below 122.0.6261.57, system is vulnerable.

Check Version:

chrome://version/ or 'google-chrome --version' on Linux/macOS

Verify Fix Applied:

Confirm Chrome version is 122.0.6261.57 or higher in About Google Chrome page.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with DevTools references
  • Unexpected Chrome process termination

Network Indicators:

  • Requests to suspicious domains with crafted HTML payloads

SIEM Query:

source="chrome_crash_reports" AND message="DevTools" OR source="proxy_logs" AND url CONTAINS "suspicious_domain"

🔗 References

📤 Share & Export