CVE-2024-7018

7.8 HIGH

📋 TL;DR

A heap buffer overflow vulnerability in Chrome's PDF renderer allows remote attackers to execute arbitrary code or cause denial of service via specially crafted PDF files. This affects all Chrome users on vulnerable versions who open malicious PDFs.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: All versions prior to 124.0.6367.78
Operating Systems: Windows, macOS, Linux, Android, iOS
Default Config Vulnerable: ⚠️ Yes
Notes: All default Chrome installations are vulnerable. Other Chromium-based browsers may be affected if using vulnerable PDF rendering components.

📦 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 ransomware deployment.

🟠

Likely Case

Browser crash (denial of service) or limited memory corruption leading to instability.

🟢

If Mitigated

No impact if patched or if PDFs are opened in sandboxed environments.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

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

Exploitation requires user interaction (opening a malicious PDF). Chrome's sandbox provides some mitigation against full system compromise.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 124.0.6367.78

Vendor Advisory: https://issues.chromium.org/issues/333414305

Restart Required: Yes

Instructions:

1. Open Chrome. 2. Click menu (three dots) → 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 Chrome PDF Viewer

all

Force PDFs to open in external applications instead of Chrome's built-in PDF renderer.

chrome://settings/content/pdfDocuments → Toggle 'Download PDF files instead of automatically opening them in Chrome'

Use PDF Viewer Extension

all

Install a third-party PDF viewer extension that doesn't use Chrome's vulnerable PDF component.

🧯 If You Can't Patch

  • Block PDF file downloads at network perimeter or email gateways.
  • Educate users to avoid opening PDFs from untrusted sources.

🔍 How to Verify

Check if Vulnerable:

Check Chrome version: chrome://settings/help. If version is below 124.0.6367.78, system is vulnerable.

Check Version:

On Windows: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version
On macOS: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
On Linux: google-chrome --version

Verify Fix Applied:

Confirm Chrome version is 124.0.6367.78 or higher via chrome://settings/help.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with PDF-related stack traces
  • Unexpected Chrome process terminations when opening PDFs

Network Indicators:

  • PDF file downloads from suspicious sources
  • Unusual PDF file sizes or structures

SIEM Query:

source="chrome_crash_logs" AND (process="chrome" OR process="chrome_renderer") AND message="*pdf*" AND severity="CRITICAL"

🔗 References

📤 Share & Export