Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-4947: Type Confusion in Google Chrome

0
Critical
VulnerabilityCVE-2024-4947cvecve-2024-4947
Published: Wed May 15 2024 (05/15/2024, 20:42:34 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 22:33:47 UTC

Technical Analysis

CVE-2024-4947 is a critical security vulnerability identified in the V8 JavaScript engine component of Google Chrome prior to version 125.0.6422.60. The vulnerability is classified as a type confusion flaw (CWE-843), where the engine incorrectly handles object types during execution, leading to memory corruption. This flaw can be exploited remotely by an attacker who crafts a malicious HTML page that, when loaded by a victim's browser, triggers the type confusion bug. The consequence is arbitrary code execution within the sandbox environment of Chrome, allowing the attacker to potentially execute malicious payloads with the same privileges as the browser process. The CVSS v3.1 base score is 9.6 (critical), indicating a vulnerability that is remotely exploitable over the network (AV:N), requires no privileges (PR:N), but does require user interaction (UI:R). The scope is changed (S:C), meaning the vulnerability can affect components beyond the initially vulnerable one, and it impacts confidentiality, integrity, and availability to a high degree (C:H/I:H/A:H). Although there are no known exploits in the wild at the time of publication, the severity and ease of exploitation make it a high-priority issue. The vulnerability affects all Chrome users running versions prior to the fixed release, which is significant given Chrome's dominant market share in web browsers globally. The lack of patch links in the provided data suggests users should update directly via official Chrome update channels. This vulnerability underscores the importance of timely patching and monitoring for potential exploitation attempts.

Potential Impact

The impact of CVE-2024-4947 is severe for organizations worldwide due to the widespread use of Google Chrome as a primary web browser. Successful exploitation allows remote attackers to execute arbitrary code within the browser sandbox, potentially leading to full system compromise if sandbox escapes are chained. This can result in data theft, installation of persistent malware, espionage, or disruption of services. Confidentiality, integrity, and availability of affected systems are all at high risk. Organizations relying on Chrome for web access, including enterprises, governments, and critical infrastructure, face increased risk of targeted attacks or mass exploitation campaigns. The requirement for user interaction (visiting a malicious page) means phishing or drive-by download attacks are likely vectors. The vulnerability's presence in a core browser component also complicates detection and mitigation, as attackers can leverage it to bypass traditional endpoint defenses. Failure to patch promptly could lead to widespread exploitation, especially as proof-of-concept exploits may emerge given the public disclosure.

Mitigation Recommendations

To mitigate CVE-2024-4947, organizations should immediately update all instances of Google Chrome to version 125.0.6422.60 or later, where the vulnerability is fixed. Since no direct patch links were provided, users should rely on official Chrome update mechanisms or enterprise deployment tools to ensure timely updates. Additionally, organizations should implement network-level protections such as web filtering to block access to known malicious sites and employ endpoint detection and response (EDR) solutions capable of detecting anomalous browser behavior. Browser isolation or sandboxing technologies can reduce the risk of exploitation by isolating web content execution. User awareness training is critical to reduce the likelihood of users visiting malicious pages, emphasizing caution with unsolicited links and attachments. Monitoring threat intelligence feeds for emerging exploits related to this CVE is recommended to enable rapid response. Finally, consider restricting or disabling JavaScript execution in high-risk environments where feasible, or using browser extensions that enforce script control policies.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Chrome
Date Reserved
2024-05-15T15:27:54.853Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f7d9b5247d717aace26bb9

Added to database: 10/21/2025, 7:06:29 PM

Last enriched: 2/27/2026, 10:33:47 PM

Last updated: 3/24/2026, 10:33:34 PM

Views: 129

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses