CVE-2020-15969

8.8 HIGH

📋 TL;DR

This vulnerability is a use-after-free memory corruption flaw in Chrome's WebRTC component. It allows remote attackers to potentially execute arbitrary code or cause denial of service by tricking users into visiting a malicious webpage. All Chrome users prior to version 86.0.4240.75 are affected.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: All versions prior to 86.0.4240.75
Operating Systems: Windows, macOS, Linux, Android, Chrome OS
Default Config Vulnerable: ⚠️ Yes
Notes: All standard Chrome installations are vulnerable. WebRTC is enabled by default.

📦 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 →

Macos by Apple

macOS is Apple's desktop and laptop operating system powering Mac computers used by millions of professionals, developers, creative professionals, and enterprise users worldwide. Built on a Unix foundation with the Darwin kernel and modern Cocoa frameworks, macOS delivers a seamless ecosystem integr...

Learn more about Macos →

⚠️ 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 code execution within browser sandbox.

🟢

If Mitigated

No impact if Chrome is updated to patched version or workarounds are applied.

🌐 Internet-Facing: HIGH - Exploitable via malicious websites without user interaction beyond visiting the page.
🏢 Internal Only: MEDIUM - Requires user to visit malicious internal page, but internal threats exist.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires bypassing Chrome's sandbox and ASLR, but use-after-free vulnerabilities are commonly exploited.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 86.0.4240.75 and later

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

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.

🔧 Temporary Workarounds

Disable WebRTC

all

Temporarily disable WebRTC functionality to prevent exploitation.

chrome://flags/#disable-webrtc
Set 'WebRTC' flag to 'Disabled'

Use Chrome Enterprise policies

windows

Deploy group policies to disable WebRTC or enforce Chrome updates.

Configure 'DefaultWebRtcSetting' policy to 2 (disable)
Configure 'AutoUpdateCheckPeriodMinutes' to enforce updates

🧯 If You Can't Patch

  • Use alternative browsers without WebRTC vulnerabilities
  • Implement network filtering to block malicious websites and restrict browser usage

🔍 How to Verify

Check if Vulnerable:

Check Chrome version: if below 86.0.4240.75, system is vulnerable.

Check Version:

chrome://version/ (on Chrome) or 'google-chrome --version' (command line)

Verify Fix Applied:

Confirm Chrome version is 86.0.4240.75 or higher after update.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with WebRTC-related modules
  • Unexpected Chrome process termination

Network Indicators:

  • Unusual WebRTC connections to external IPs
  • Suspicious JavaScript loading WebRTC APIs

SIEM Query:

source="chrome_crash_logs" AND (process="chrome" OR module="webrtc") AND event="crash"

🔗 References

📤 Share & Export