What is Chromium V8?
V8 is Google's open-source JavaScript and WebAssembly engine powering Chrome, Edge, Opera, and all Chromium-based applications. Its Turbofan JIT compiler optimizes frequently executed JavaScript code for performance by making type assumptions about objects — assumptions that, if violated through attacker-controlled JavaScript, can result in type confusion and heap corruption. Type confusion vulnerabilities in V8 are among the most reliably exploitable browser security flaws and are frequently targeted by state-sponsored groups and commercial spyware vendors.
Overview
CVE-2024-4947 is a type confusion vulnerability in V8's Turbofan JIT compiler that allows a remote attacker to achieve heap corruption via a crafted HTML page visited in any Chromium-based browser. Exploited as a zero-day and patched in Chrome 124.0.6367.201/.202 on May 15, 2024, it was added to the CISA KEV catalog five days later. It is one of three V8 type confusion zero-days patched within a two-week span in May 2024 (alongside CVE-2024-4671 and followed by CVE-2024-5274 on May 28), reflecting a period of intense V8 zero-day activity linked to nation-state threat actors.
Affected Versions
| Browser | Vulnerable | Fixed |
|---|---|---|
| Google Chrome | < 124.0.6367.201 (Linux) / .202 (Windows/Mac) | 124.0.6367.201/.202 |
| Microsoft Edge | Prior to equivalent patch | Corresponding Edge update |
| Other Chromium-based browsers | Prior to backport | Per vendor update |
Technical Details
CWE-843 (Type Confusion). Turbofan, V8's optimizing JIT compiler, speculatively compiles JavaScript based on type information observed at runtime. When an attacker crafts JavaScript that invalidates Turbofan's type assumptions after compilation — a technique known as type confusion — the compiled code reads or writes memory using incorrect type layouts, corrupting the heap. The typical exploit chain proceeds:
- V8 type confusion → controlled heap corruption.
- Use corruption to build arbitrary read/write primitives.
- Execute code within the Chrome renderer sandbox.
- Chain with a sandbox escape (a separate vulnerability) for full OS code execution.
The renderer sandbox limits the initial impact to browser-process memory; a complete exploit requires a second bug for sandbox escape.
Discovery
Reported to Google. The rapid succession of V8 zero-days in May 2024 (CVE-2024-4671 on May 9, CVE-2024-4947 on May 15, CVE-2024-5274 on May 28) suggests either multiple independent researchers discovering related bugs, or a single threat actor using a chain of V8 bugs before each is caught and patched.
Exploitation Context
Active exploitation was confirmed, prompting the May 20, 2024 CISA KEV addition. The 2024 V8 zero-day cluster was associated with campaigns targeting cryptocurrency industry employees, financial sector workers, and government officials — profiles consistent with North Korea-linked APTs (Lazarus Group, Citrine Sleet) who routinely use browser zero-day chains to deploy cryptocurrency-theft and espionage implants. The Chromium update cycle (stable channel) typically delivers patches to users within hours of release via auto-update.
Remediation
- Update Chrome to 124.0.6367.201 (Linux) or .202 (Windows/Mac) or any later version.
- Update Microsoft Edge and other Chromium-based browsers to the corresponding patched releases.
- Enable automatic browser updates — Chrome's auto-update mechanism is one of the fastest security update pipelines available for any software product.
- Organizations should enforce minimum Chrome version via policy (Chrome Enterprise) and block outdated browser versions from accessing enterprise resources.
Key Details
| Property | Value |
|---|---|
| CVE ID | CVE-2024-4947 |
| Vendor / Product | Google — Chromium V8 |
| NVD Published | 2024-05-15 |
| NVD Last Modified | 2025-10-24 |
| CVSS 3.1 Score | 9.6 |
| CVSS 3.1 Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| Severity | CRITICAL |
| CWE | CWE-843 find similar ↗ |
| CISA KEV Added | 2024-05-20 |
| CISA KEV Deadline | 2024-06-10 |
| Known Ransomware Use | No |
CVSS 3.1 Breakdown
Required Action
Timeline
| Date | Event |
|---|---|
| 2024-05-15 | Google releases Chrome 124.0.6367.201/.202 patching CVE-2024-4947; exploitation confirmed in the wild |
| 2024-05-20 | Added to CISA Known Exploited Vulnerabilities catalog |
| 2024-06-10 | CISA BOD 22-01 remediation deadline |
References
| Resource | Type |
|---|---|
| Chrome Stable Channel Update — May 15, 2024 | Vendor Advisory |
| NVD — CVE-2024-4947 | Vulnerability Database |
| CISA KEV Catalog Entry | US Government |