CVE-2022-1135
📋 TL;DR
This vulnerability is a use-after-free memory corruption flaw in Google Chrome's Shopping Cart feature that allows a remote attacker to potentially exploit heap corruption through standard user interactions. It affects all users running Chrome versions prior to 100.0.4896.60, potentially leading to arbitrary code execution.
💻 Affected Systems
- Google 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
Remote code execution with the same privileges as the Chrome process, potentially leading to full system compromise, data theft, or malware installation.
Likely Case
Browser crash (denial of service) or limited code execution within the sandboxed Chrome process.
If Mitigated
No impact if Chrome is fully patched or if exploit attempts are blocked by security controls.
🎯 Exploit Status
Exploitation requires user interaction (visiting malicious site or clicking malicious content) but no authentication. Memory corruption vulnerabilities in Chrome are frequently exploited in the wild.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 100.0.4896.60 and later
Vendor Advisory: https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_29.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 with the patched version.
🔧 Temporary Workarounds
Disable Shopping Cart feature
allTemporarily disable the Shopping Cart feature that contains the vulnerability
chrome://flags/#enable-shopping-list → Disabled
Use Chrome sandboxing
allEnsure Chrome sandbox is enabled to limit impact of potential exploitation
chrome://flags/#enable-site-per-process → Enabled
chrome://flags/#enable-sandbox → Enabled
🧯 If You Can't Patch
- Implement web filtering to block known malicious sites and restrict access to untrusted websites
- Use application whitelisting to prevent execution of unauthorized binaries that might result from exploitation
🔍 How to Verify
Check if Vulnerable:
Check Chrome version: If version is less than 100.0.4896.60, system is vulnerable.Check Version:
chrome://version or 'google-chrome --version' (Linux) or check in Chrome settingsVerify Fix Applied:
Confirm Chrome version is 100.0.4896.60 or higher via chrome://version📡 Detection & Monitoring
Log Indicators:
- Chrome crash reports with memory corruption signatures
- Unexpected Chrome process termination
- Security event logs showing Chrome accessing unusual system resources
Network Indicators:
- Traffic to known exploit delivery domains
- Unusual outbound connections from Chrome processes
SIEM Query:
process_name:"chrome.exe" AND (event_id:1000 OR event_id:1001) AND description:"EXCEPTION_ACCESS_VIOLATION" OR process_name:"chrome.exe" AND parent_process NOT IN ("explorer.exe", "userinit.exe")🔗 References
- https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_29.html
- https://crbug.com/1285601
- https://security.gentoo.org/glsa/202208-25
- https://chromereleases.googleblog.com/2022/03/stable-channel-update-for-desktop_29.html
- https://crbug.com/1285601
- https://security.gentoo.org/glsa/202208-25
