CVE-2024-8193

8.8 HIGH

📋 TL;DR

This vulnerability allows remote attackers to exploit heap corruption in Chrome's Skia graphics engine via a crafted HTML page. Attackers who have already compromised the renderer process can potentially execute arbitrary code or cause crashes. All Chrome users on affected versions are at risk.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: All versions prior to 128.0.6613.113
Operating Systems: Windows, macOS, Linux, Android, iOS
Default Config Vulnerable: ⚠️ Yes
Notes: All default Chrome configurations are vulnerable. The vulnerability is in the Skia graphics library used by Chrome.

📦 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

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

🟠

Likely Case

Renderer process crash leading to denial of service, or limited sandbox escape enabling further exploitation.

🟢

If Mitigated

Sandbox containment prevents full system compromise, but renderer crashes still cause service disruption.

🌐 Internet-Facing: HIGH - Attackers can exploit via malicious websites without user interaction beyond visiting the site.
🏢 Internal Only: MEDIUM - Requires initial renderer compromise, but internal threats could still exploit this vulnerability.

🎯 Exploit Status

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

Requires renderer process compromise first, but then allows heap corruption exploitation. No public exploit code has been disclosed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 128.0.6613.113 and later

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

Restart Required: Yes

Instructions:

1. Open Chrome. 2. Click the three-dot menu. 3. Go to Help > About Google Chrome. 4. Chrome will automatically check for and install updates. 5. Click Relaunch to restart Chrome with the fixed version.

🔧 Temporary Workarounds

Disable JavaScript

all

Prevents execution of malicious JavaScript that could trigger the vulnerability

chrome://settings/content/javascript
Toggle 'Allowed (recommended)' to 'Blocked'

Use Site Isolation

all

Enhances sandboxing between websites to limit impact

chrome://flags/#site-isolation-trial-opt-out
Set to 'Disabled'

🧯 If You Can't Patch

  • Implement network filtering to block malicious websites and content
  • Use application control to restrict Chrome usage to trusted sites only

🔍 How to Verify

Check if Vulnerable:

Check Chrome version in Settings > About Chrome. If version is below 128.0.6613.113, the system is vulnerable.

Check Version:

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

Verify Fix Applied:

Confirm Chrome version is 128.0.6613.113 or higher after update and restart.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with SIGSEGV or heap corruption errors
  • Renderer process termination events
  • Skia-related error messages in Chrome logs

Network Indicators:

  • Unusual traffic to/from Chrome processes
  • Multiple rapid connections to suspicious domains

SIEM Query:

source="chrome" AND (event_type="crash" OR message="*heap*" OR message="*Skia*")

🔗 References

📤 Share & Export