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-4761: Out of bounds write in Google Chrome

0
High
VulnerabilityCVE-2024-4761cvecve-2024-4761
Published: Tue May 14 2024 (05/14/2024, 02:09:53 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Out of bounds write in V8 in Google Chrome prior to 124.0.6367.207 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

AI-Powered Analysis

AILast updated: 12/26/2025, 16:33:57 UTC

Technical Analysis

CVE-2024-4761 is an out-of-bounds write vulnerability identified in the V8 JavaScript engine component of Google Chrome prior to version 124.0.6367.207. The vulnerability arises from improper bounds checking during memory operations, classified under CWE-787. An attacker can craft a malicious HTML page that, when rendered by the vulnerable Chrome browser, triggers an out-of-bounds write in memory. This memory corruption can lead to arbitrary code execution, allowing the attacker to execute code in the context of the browser process. The attack vector is remote network (AV:N), requiring no privileges (PR:N) but does require user interaction (UI:R), such as visiting a malicious or compromised website. The scope is changed (S:C), meaning the vulnerability can affect resources beyond the initially compromised component, impacting confidentiality, integrity, and availability (all rated high). Although no exploits have been reported in the wild yet, the high CVSS score (8.3) and the nature of the vulnerability make it a critical risk for users of affected Chrome versions. The vulnerability was published on May 14, 2024, and Google has released a patched version (124.0.6367.207) to address it. The absence of known exploits suggests a window for proactive patching and mitigation. This vulnerability is particularly dangerous because V8 is a core engine used to execute JavaScript, a ubiquitous web technology, making the attack surface broad and the potential impact significant.

Potential Impact

For European organizations, the impact of CVE-2024-4761 can be severe. Since Google Chrome is widely used across enterprises, government agencies, and public institutions in Europe, a successful exploit could lead to unauthorized code execution, data breaches, and disruption of critical services. Confidential information handled within browsers, such as credentials, personal data, and corporate secrets, could be exposed or manipulated. The integrity of systems could be compromised, allowing attackers to implant persistent malware or pivot within networks. Availability could also be affected if the exploit leads to browser crashes or system instability. Organizations with high web exposure, such as financial institutions, healthcare providers, and critical infrastructure operators, are at elevated risk. The requirement for user interaction means phishing or social engineering campaigns could be used to trigger exploitation. The lack of known exploits currently provides a critical window for mitigation before widespread attacks emerge.

Mitigation Recommendations

1. Immediate update of all Google Chrome installations to version 124.0.6367.207 or later to apply the official patch. 2. Enforce strict browser update policies across organizational endpoints to prevent use of vulnerable versions. 3. Implement network-level protections such as web filtering and intrusion prevention systems to block access to known malicious sites. 4. Deploy Content Security Policy (CSP) headers to restrict the execution of untrusted scripts and reduce attack surface. 5. Educate users about phishing and social engineering tactics that could lead to visiting malicious web pages. 6. Use browser sandboxing and endpoint detection and response (EDR) tools to detect and contain suspicious behavior. 7. Monitor security advisories and threat intelligence feeds for emerging exploit reports related to this CVE. 8. Consider disabling or restricting JavaScript execution in high-risk environments where feasible. 9. Conduct regular vulnerability scanning and penetration testing to identify and remediate residual risks related to browser vulnerabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Chrome
Date Reserved
2024-05-10T15:52:59.148Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68f7d9b5247d717aace26ba6

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

Last enriched: 12/26/2025, 4:33:57 PM

Last updated: 2/7/2026, 5:15:14 PM

Views: 78

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats