CVE-2022-0103

8.8 HIGH

📋 TL;DR

This vulnerability is a use-after-free memory corruption flaw in SwiftShader, a software rendering component of Google Chrome. It allows remote attackers to potentially execute arbitrary code or cause denial of service by tricking users into visiting a malicious HTML page. All Chrome users prior to version 97.0.4692.71 are affected.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: All versions prior to 97.0.4692.71
Operating Systems: Windows, Linux, macOS, Android, iOS
Default Config Vulnerable: ⚠️ Yes
Notes: SwiftShader is enabled by default when hardware acceleration is unavailable or disabled.

📦 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 with the same privileges as the Chrome process, potentially leading to full system compromise if Chrome runs with elevated privileges.

🟠

Likely Case

Browser crash (denial of service) or limited code execution within Chrome's sandbox, potentially allowing data theft or further exploitation.

🟢

If Mitigated

Browser crash with no data loss if sandboxing works correctly, though repeated crashes could impact productivity.

🌐 Internet-Facing: HIGH - Exploitation requires only visiting a malicious webpage, which is common for internet-facing systems.
🏢 Internal Only: MEDIUM - Internal users could still be targeted via phishing or compromised internal websites.

🎯 Exploit Status

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

Use-after-free vulnerabilities in browser components are frequently exploited in the wild, though no specific weaponization of this CVE has been confirmed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 97.0.4692.71 and later

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

Restart Required: Yes

Instructions:

1. Open Chrome. 2. Click the three-dot menu → Help → About Google Chrome. 3. Chrome will automatically check for and apply updates. 4. Click 'Relaunch' to restart Chrome with the updated version.

🔧 Temporary Workarounds

Disable SwiftShader

all

Disable software rendering via SwiftShader to prevent exploitation, though this may impact performance on systems without hardware acceleration.

chrome://flags/#disable-software-rasterizer → Disable

Enable Site Isolation

all

Enforce site isolation to limit the impact of potential exploitation.

chrome://flags/#enable-site-per-process → Enable

🧯 If You Can't Patch

  • Restrict browser usage to trusted websites only using network policies or web filtering.
  • Implement application whitelisting to prevent execution of malicious code from browser exploits.

🔍 How to Verify

Check if Vulnerable:

Check Chrome version via chrome://settings/help or 'About Google Chrome' in menu.

Check Version:

On Linux: google-chrome --version; On Windows: reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version

Verify Fix Applied:

Confirm Chrome version is 97.0.4692.71 or higher.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with SwiftShader-related stack traces
  • Unexpected Chrome process termination events in system logs

Network Indicators:

  • Unusual outbound connections from Chrome processes post-crash
  • Requests to known exploit hosting domains

SIEM Query:

source="chrome_crash_logs" AND ("SwiftShader" OR "ANGLE") AND severity=CRITICAL

🔗 References

📤 Share & Export