CVE-2024-4947: Google Chromium V8 Type Confusion Vulnerability

What it is

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)

Exploitation evidence

First exploit evidence seen: 2024-05-20 (earliest date across the sources below).

Exploited in the wild

• CISA KEV: listed since 2024-05-20. Source

Public exploit code

GitHub proof-of-concept repositories

2 public repositories from 2 accounts, first seen 2025-07-21. Most starred: bjrjk/CVE-2024-4947 (32 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

How to fix it

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

• google chrome: upgrade to 125.0.6422.60 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_15.html (CISA KEV notes)

MITRE ATT&CK mitigations for this chain

• M1050 Exploit Protection (for T1189) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploit
• M1051 Update Software (for T1189) : Ensuring that all browsers and plugins are kept updated can help prevent the exploit phase of this technique. Use modern browsers with security features turned on.
• M1048 Application Isolation and Sandboxing (for T1189) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. The risks of additional exploits and weaknesses in implementation may still exist
• M1021 Restrict Web-Based Content (for T1189, T1059) : Adblockers can help prevent malicious code served through ads from executing in the first place. Script blocking extensions can also help to prevent the execution of JavaScript. Consider disabling browser push notifications from certain applications and browsers.
• M1017 User Training (for T1189) : Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction.
• M1033 Limit Software Installation (for T1059) : Prevent user installation of unrequired command and scripting interpreters.
• M1045 Code Signing (for T1059) : Where possible, only permit execution of signed scripts.
• M1042 Disable or Remove Feature or Program (for T1059) : Disable or remove any unnecessary or unused shells or interpreters.
• M1038 Execution Prevention (for T1059) : Use application control where appropriate. For example, PowerShell Constrained Language mode can be used to restrict access to sensitive or otherwise dangerous language elements such as those used to execute arbitrary Windows APIs or files (e.g., `Add-Type`).
• M1049 Antivirus/Antimalware (for T1059) : Anti-virus can be used to automatically quarantine suspicious files.

Detection Generic guidance

• Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.