CVE-2025-0437

8.8 HIGH

📋 TL;DR

This vulnerability allows a remote attacker to trigger an out-of-bounds read in Chrome's Metrics component via a crafted HTML page, potentially leading to heap corruption. All users running vulnerable versions of Google Chrome are affected. The attacker could exploit this to execute arbitrary code or cause denial of service.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: Prior to 132.0.6834.83
Operating Systems: Windows, macOS, Linux, ChromeOS
Default Config Vulnerable: ⚠️ Yes
Notes: All standard Chrome installations are vulnerable. Extensions or security settings don't mitigate this.

📦 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 installation of persistent malware.

🟠

Likely Case

Browser crash (denial of service) or limited information disclosure from memory.

🟢

If Mitigated

Browser sandbox may contain the damage to the browser process only, preventing full system compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires user interaction (visiting malicious site) but no authentication. Heap corruption exploitation is non-trivial but feasible.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 132.0.6834.83 or later

Vendor Advisory: https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_14.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 JavaScript

all

Prevents execution of malicious scripts that could trigger the vulnerability

chrome://settings/content/javascript → Block

Use site isolation

all

Limits impact by isolating websites in separate processes (already enabled by default in modern Chrome)

chrome://flags/#site-isolation-trial-opt-out → Disabled

🧯 If You Can't Patch

  • Deploy network filtering to block known malicious sites and scripts
  • Use application allowlisting to restrict browser execution to trusted instances only

🔍 How to Verify

Check if Vulnerable:

Check Chrome version: if earlier than 132.0.6834.83, you are vulnerable.

Check Version:

On Chrome: chrome://version/ or Command Line: google-chrome --version

Verify Fix Applied:

Confirm Chrome version is 132.0.6834.83 or later after update.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with exception codes like ACCESS_VIOLATION
  • Unexpected browser process termination in system logs

Network Indicators:

  • Requests to unusual domains with crafted HTML/JS payloads
  • Multiple users accessing same malicious site

SIEM Query:

source="chrome_crash_reports" AND (exception_code="0xc0000005" OR process_name="chrome.exe")

🔗 References

📤 Share & Export