CVE DatabaseCVE-2024-4761
한국어 권고문 →
CVE-2024-47618.8/HIGHCISA KEVCWE-787CWE-787

Google Chrome V8 Engine Out-of-bounds Write Vulnerability (CVE-2024-4761) Technical Analysis and Hardening Guide

⚡ Jump to Patch
Affected Vendors
google, chromium
Affected Components
chrome, chromium
Published Date
2024-05-14
CVSS v3.1
8.8
HIGH
EPSS (30d)
11.0%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Google Chrome and Chromium-based browsers prior to version 124.0.6367.207

Impact

A remote attacker can trigger an out-of-bounds memory write via a crafted HTML page, potentially leading to arbitrary code execution or denial of service (DoS)

Mitigation

Immediately update Google Chrome to the latest stable version (124.0.6367.207 or higher) and enforce automatic update policies across the enterprise

Affected Products & Version Scope

Google Chrome prior to version 124.0.6367.207 on Windows, macOS, and Linux, as well as other browsers utilizing the Chromium engine

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

To upgrade Google Chrome to the patched version on Linux (Ubuntu/Debian-based systems), execute the following commands:

bash
# Update package repositories and upgrade Google Chrome to the latest version
sudo apt-get update && sudo apt-get --only-upgrade install google-chrome-stable -y

# Verify the installed version
google-chrome --version

2. Temporary Workaround & Hardening Configuration

If immediate patching is not feasible, enforce security policies such as Renderer Code Integrity via Windows Registry to mitigate exploitation risks:

powershell
# Enable Renderer Code Integrity protection for Google Chrome
$RegistryPath = 'HKLM:\SOFTWARE\Policies\Google\Chrome'
if (-not (Test-Path $RegistryPath)) {
    New-Item -Path $RegistryPath -Force
}
New-ItemProperty -Path $RegistryPath -Name 'RendererCodeIntegrityEnabled' -Value 1 -PropertyType DWord -Force

3. Log Audit & IoC Verification Commands

Use the following PowerShell script to audit enterprise endpoints and identify vulnerable installations of Google Chrome:

powershell
# Audit script to check local Google Chrome version
$ChromePath = '${Env:ProgramFiles}\Google\Chrome\Application\chrome.exe'
if (Test-Path $ChromePath) {
    $Version = [System.Diagnostics.FileVersionInfo]::GetVersionInfo($ChromePath).FileVersion
    Write-Host 'Current Chrome Version:' $Version
    if ([System.Version]$Version -lt [System.Version]'124.0.6367.207') {
        Write-Warning 'Vulnerable version detected! Upgrade is highly recommended.'
    } else {
        Write-Host 'Chrome is up-to-date and secure.' -ForegroundColor Green
    }
} else {
    Write-Host 'Google Chrome is not installed in the default path.'
}
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Due to active exploitation in the wild, immediately update all Google Chrome installations to version 124.0.6367.207 or later.

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-2024-4761) is an out-of-bounds write (CWE-787) in the V8 JavaScript and WebAssembly engine of Google Chrome and Chromium. The root cause lies in V8's dynamic memory management and array/object index validation mechanisms. Due to insufficient boundary checks, the engine fails to restrict write operations within the allocated buffer limits, allowing memory corruption beyond the intended boundaries.

2. Exploitation Mechanics & Attack Scenario

An attacker exploits this vulnerability by hosting a specially crafted HTML page containing malicious JavaScript code designed to manipulate V8's memory allocation. When a victim visits the malicious page, the browser parses and executes the script, triggering an out-of-bounds write in the heap memory. This allows the attacker to overwrite critical adjacent memory structures or function pointers, hijacking the control flow of the renderer process to execute arbitrary code within the sandbox.

3. Infrastructure & Business Impact

As this vulnerability is actively exploited in the wild (listed in CISA KEV), it poses an immediate threat to enterprise environments. Successful exploitation grants the attacker control over the browser's renderer process. If chained with a sandbox escape vulnerability, the attacker can compromise the underlying operating system, leading to unauthorized access, data exfiltration, and potential lateral movement within the corporate network.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2024-4761)

FAQ

Q1. How critical is CVE-2024-4761 and is it actively exploited in the wild?

CVE-2024-4761 is rated CVSS 8.8 (HIGH) with a 30-day EPSS exploitation probability of 11.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-2024-4761?

Primary impacted vendors include google, chromium across chrome, chromium. Scope summary: Google Chrome prior to version 124.0.6367.207 on Windows, macOS, and Linux, as well as other browsers utilizing the Chromium engine

Q3. What temporary mitigations or workarounds exist for CVE-2024-4761 before patching?

[Mitigation] Immediately update Google Chrome to the latest stable version (124.0.6367.207 or higher) and enforce automatic update policies across the enterprise 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-2024-4761

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-2024-4761 Google Chrome V8 Engine Out-of-bounds Write Vulnerability (CVE-2024-4761) Technical Analysis and Hardening Guide (CVSS 8.8) - Patch & Workaround | CVE Pulse