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-0519: Out of bounds memory access in Google Chrome

0
High
VulnerabilityCVE-2024-0519cvecve-2024-0519
Published: Tue Jan 16 2024 (01/16/2024, 21:14:49 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 11:02:58 UTC

Technical Analysis

CVE-2024-0519 is a critical memory safety vulnerability classified under CWE-125 (Out-of-bounds Read) and CWE-787 (Out-of-bounds Write) affecting the V8 JavaScript engine component of Google Chrome prior to version 120.0.6099.224. The flaw arises from improper bounds checking during memory operations, allowing an attacker to perform out-of-bounds memory access. By delivering a specially crafted HTML page containing malicious JavaScript, a remote attacker can trigger heap corruption within the browser's memory space. This corruption can lead to arbitrary code execution, enabling the attacker to execute malicious payloads with the privileges of the user running Chrome. The vulnerability requires no prior authentication but does require user interaction, such as visiting a malicious or compromised website. The CVSS v3.1 score of 8.8 reflects the high impact on confidentiality, integrity, and availability, combined with network attack vector, low attack complexity, no privileges required, and user interaction needed. While no exploits are currently known in the wild, the vulnerability's nature and impact make it a high priority for patching. The lack of patch links in the provided data suggests that users should monitor official Google Chrome security advisories for updates. The vulnerability underscores the critical importance of memory safety in browser engines and the risks posed by complex JavaScript execution environments.

Potential Impact

The exploitation of CVE-2024-0519 can have severe consequences for organizations globally. Successful attacks can lead to arbitrary code execution within the context of the user's browser, potentially allowing attackers to steal sensitive information, install malware, or pivot to internal networks. The compromise of confidentiality, integrity, and availability can affect corporate data, user credentials, and critical web applications accessed via Chrome. Given Chrome's dominant market share in desktop and mobile browsers worldwide, the attack surface is extensive. Organizations relying on Chrome for business operations, especially those handling sensitive or regulated data, face increased risk. The requirement for user interaction means phishing or social engineering campaigns could be used to lure victims to malicious sites. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, as proof-of-concept exploits could emerge rapidly. The vulnerability also poses risks to critical infrastructure sectors, including finance, healthcare, and government, where browser compromise can lead to broader systemic impacts.

Mitigation Recommendations

To mitigate CVE-2024-0519, organizations should immediately update Google Chrome to version 120.0.6099.224 or later once available. Until patches are applied, restrict access to untrusted or suspicious websites through network filtering and web proxy solutions. Employ browser security features such as sandboxing, site isolation, and strict content security policies to limit the impact of potential exploitation. Educate users about the risks of interacting with unknown links or websites to reduce the likelihood of triggering the vulnerability. Deploy endpoint detection and response (EDR) tools capable of identifying anomalous browser behavior indicative of exploitation attempts. For high-security environments, consider using browser isolation technologies or alternative browsers with different JavaScript engines as a temporary measure. Continuously monitor threat intelligence feeds for emerging exploit reports and update incident response plans accordingly. Finally, maintain a robust patch management process to ensure timely deployment of browser updates.

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-01-12T22:48:07.982Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f7d9b0247d717aace26899

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

Last enriched: 2/28/2026, 11:02:58 AM

Last updated: 3/25/2026, 1:38:38 AM

Views: 50

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