SentinelOne
CVE Vulnerability Database

CVE-2024-5274: Google Chrome V8 Type Confusion RCE Flaw

CVE-2024-5274 is a type confusion vulnerability in Google Chrome's V8 JavaScript engine that enables remote code execution within a sandbox via malicious HTML pages. This article covers technical details, affected versions, and mitigation.

Updated:

CVE-2024-5274 Overview

Type Confusion in V8 in Google Chrome prior to 125.0.6422.112 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Critical Impact

This vulnerability allows for remote code execution with high impact on confidentiality, integrity, and availability.

Affected Products

  • google chrome
  • fedoraproject fedora

Discovery Timeline

  • Not Available - Vulnerability discovered by Not Available
  • Not Available - Responsible disclosure to google
  • Not Available - CVE CVE-2024-5274 assigned
  • Not Available - google releases security patch
  • 2024-05-28 - CVE CVE-2024-5274 published to NVD
  • 2025-10-24 - Last updated in NVD database

Technical Details for CVE-2024-5274

Vulnerability Analysis

This vulnerability arises from a type confusion flaw within the V8 engine used by Google Chrome, which can be exploited when a user visits a specially crafted webpage. The flaw allows an attacker to perform arbitrary code execution within the Chrome sandbox environment, exploiting the incorrect handling of object types.

Root Cause

The root cause is the improper handling and casting of object types in the V8 engine, leading to a type confusion error.

Attack Vector

The attack vector for this vulnerability is through network access. An attacker would need to craft a malicious HTML page and deceive users into opening it in an unpatched version of Google Chrome.

javascript
// Example exploitation code (sanitized)
function exploit() {
    var craftedObject = { a: 0x41414141 };
    var overflow = [craftedObject];
    // Manipulate object types
    overflow[0] = "string";
    // Trigger type confusion
    var vulnerabilityTrigger = [].concat(overflow);
}

Detection Methods for CVE-2024-5274

Indicators of Compromise

  • Unusual CPU usage by chrome.exe
  • Unexpected network requests from a client's machine
  • Presence of anomalous .js files

Detection Strategies

Utilize endpoint security solutions like SentinelOne to monitor for anomalies in chrome.exe processes and network activity that may indicate exploitation attempts.

Monitoring Recommendations

Monitor system calls within the Chrome browser using EDR solutions. Set alerts for browser crashes or exceptions triggered during JavaScript execution.

How to Mitigate CVE-2024-5274

Immediate Actions Required

  • Update Google Chrome to version 125 or later.
  • Implement strict network controls to limit exposure to untrusted sites.
  • Educate users on phishing attacks and safe browsing habits.

Patch Information

Ensure that all instances of Google Chrome are updated to version 125.0.6422.112 or later to mitigate this vulnerability.

Workarounds

Consider disabling JavaScript in Chrome on critical systems as a temporary measure, although this may impact functionality.

bash
# Configuration example
sudo apt-get update && sudo apt-get --only-upgrade install google-chrome-stable

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Experience the World’s Most Advanced Cybersecurity Platform

Experience the World’s Most Advanced Cybersecurity Platform

See how our intelligent, autonomous cybersecurity platform can protect your organization now and into the future.