CVE DatabaseCVE-2021-21193
한국어 권고문 →
CVE-2021-211938.8/HIGHCISA KEVCWE-416CWE-416

Google Chrome Blink Use-After-Free Vulnerability (CVE-2021-21193) Technical Advisory

⚡ Jump to Patch
Affected Vendors
google, fedoraproject, gentoo, debian
Affected Components
chrome, chromium
Published Date
2021-03-16
CVSS v3.1
8.8
HIGH
EPSS (30d)
10.0%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Google Chrome and Chromium-based browsers prior to version 89.0.4389.90

Impact

Remote attackers can trigger heap corruption and potentially execute arbitrary code via a crafted HTML page

Mitigation

Immediately update Google Chrome and related packages to the latest stable version (89.0.4389.90 or higher)

Affected Products & Version Scope

Google Chrome versions prior to 89.0.4389.90 (Windows, macOS, Linux) and downstream Chromium-based browsers

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

The primary remediation is upgrading Google Chrome and Chromium packages to version 89.0.4389.90 or later.

For Debian/Ubuntu-based systems:

bash
sudo apt-get update && sudo apt-get --only-upgrade install google-chrome-stable -y

For RedHat/Fedora-based systems:

bash
sudo dnf upgrade chromium -y

2. Temporary Workaround & Hardening Configuration

If immediate patching is not feasible, enforce browser update policies via Group Policy (GPO) or registry settings to ensure automatic updates are not disabled by users.

PowerShell command to force Google Update policy on Windows endpoints:

powershell
New-Item -Path 'HKLM:\SOFTWARE\Policies\Google\Update' -Force | Out-Null
New-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Google\Update' -Name 'UpdateDefault' -Value 1 -PropertyType DWord -Force

3. Log Audit & IoC Verification Commands

Use the following script to audit the installed version of Google Chrome across Linux endpoints to identify vulnerable instances.

Bash script to check Chrome version:

bash
chrome_bin=$(which google-chrome 2>/dev/null)
if [ ! -z '$chrome_bin' ]; then
  version=$($chrome_bin --version | grep -oE '[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+')
  echo 'Detected Chrome Version: '$version
else
  echo 'Google Chrome is not installed on this system.'
fi
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Due to active in-the-wild exploitation, immediately update all Google Chrome installations to version 89.0.4389.90 or higher to mitigate remote code execution risks.

Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot

Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.

100% MITRE ATT&CK Detection · 1-Click Rollback

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability (CVE-2021-21193) is a Use-After-Free (UAF) flaw residing in the Blink rendering engine of Google Chrome. It occurs when the Blink engine fails to properly clear or nullify pointers to memory objects in the heap after they have been deleted or deallocated during DOM tree manipulation or style resolution. Consequently, the browser attempts to reuse these dangling pointers, leading to heap corruption.

2. Exploitation Mechanics & Attack Scenario

An attacker can exploit this vulnerability by hosting a specially crafted HTML page containing malicious DOM structures or CSS/JS payloads. When a victim visits the malicious page, the Blink engine processes the malformed content, triggering premature deallocation of a specific object. The attacker then utilizes heap grooming techniques to fill the freed memory slot with controlled data. When the engine subsequently references the stale pointer, control flow is hijacked, allowing arbitrary code execution within the context of the renderer process.

3. Infrastructure & Business Impact

As this vulnerability is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, it represents a highly active threat vector. Successful exploitation allows remote code execution (RCE) on the user's endpoint. If chained with a sandbox escape vulnerability, the attacker can compromise the underlying operating system, leading to unauthorized access to sensitive corporate data, lateral movement within the internal network, and potential ransomware deployment.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2021-21193)

FAQ

Q1. How critical is CVE-2021-21193 and is it actively exploited in the wild?

CVE-2021-21193 is rated CVSS 8.8 (HIGH) with a 30-day EPSS exploitation probability of 10.0%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2021-21193?

Primary impacted vendors include google, fedoraproject, gentoo, debian across chrome, chromium. Scope summary: Google Chrome versions prior to 89.0.4389.90 (Windows, macOS, Linux) and downstream Chromium-based browsers

Q3. What temporary mitigations or workarounds exist for CVE-2021-21193 before patching?

[Mitigation] Immediately update Google Chrome and related packages to the latest stable version (89.0.4389.90 or higher) Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2021-21193

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (google)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2021-21193 Google Chrome Blink Use-After-Free Vulnerability (CVE-2021-21193) Technical Advisory (CVSS 8.8) - Patch & Workaround | CVE Pulse