CriticalCVE-2024-0519

    Google Chromium V8 Out-of-Bounds Memory Access Vulnerability (CVE-2024-0519)

    Published In CISA KEV since Sources: SingCERT, pwn.watch, CVE.org, Debian

    What is affected, what to do

    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)

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Conflicting version data — version display is hidden until the data is resolved.

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    8.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: SingCERT, pwn.watch, CVE.org, Debian

    3.8 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 90.0

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    213.07 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    3.8 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    90.0
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 18 January 2024
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-125, CWE-787

    Response and mitigation

    Why act now?

    Prioritisation rationale

    CISA added this to KEV right after Google's emergency fix. It is a classic browser zero-day, exploited via crafted pages delivered through watering-hole or malvertising campaigns, reachable over the network without authentication and requiring only that the victim loads a page. V8 bugs like this are typically chained with a sandbox escape to gain code execution on the endpoint, and the preferred targets are users with sensitive data access or administrative rights. CISA has not flagged ransomware use, but exploitation likelihood is clearly elevated. Because virtually every workstation is exposed and the fix is low-risk to roll out, treat this as high priority: fleet-wide remediation within 24–72 hours, and immediate action for privileged workstations and internet-facing Couchbase instances.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Push Google Chrome to 120.0.6099.224 or later: Deploy via your software distribution tooling (Intune, SCCM, Jamf, Google Update). Then confirm through inventory that no install remains below that build.
      • Force a browser relaunch: Downloaded updates do nothing until the browser restarts. Set RelaunchNotification = 2 (required) and keep RelaunchNotificationPeriod to a few hours.
      • Update Microsoft Edge, Opera and other Chromium-based browsers in parallel: A patch is available from each vendor — look up the fixed version in the vendor advisory. Check each Edge channel (Stable/Extended Stable) separately.
      • Patch Fedora 38/39 endpoints: Run dnf upgrade --refresh chromium and take the fixed package version from the Fedora security advisory. Handle Flatpak and Snap installs separately.
      • Upgrade Couchbase Server to 7.2.5: Couchbase embeds V8 for Eventing and query UDFs. Locate the instances and schedule maintenance.
      • Patch high-value users first: Prioritise admin workstations, PAWs, jump hosts and finance/executive machines. Ban browsing from these systems until the patch is verified.

    2. Runbook step 2

      Mitigation layers

      • Browser configuration: Enable Edge "Enhanced security mode" (EnhanceSecurityMode, strict). It disables the V8 JIT, where most V8 exploit primitives live. In Chrome, where the deployed version supports it, set DefaultJavaScriptJitSetting = 2 and allow-list business apps via JavaScriptJitAllowedForSites.
      • Version enforcement: Use Conditional Access, Defender for Endpoint device risk or NAC posture checks to deny outdated browsers access to SaaS and intranet resources. Remove any TargetVersionPrefix pins that hold clients on old builds.
      • Network and web gateway: Block "Newly Registered Domains", "Uncategorized" and ad-network categories (malvertising) at the secure web gateway. Use remote browser isolation for high-risk user groups. Network IPS signatures for obfuscated exploit JavaScript are unreliable, so lean on reputation filtering.
      • Endpoint hardening: Enable the ASR rules "Block executable files unless they meet prevalence, age or trusted list criteria" and "Block process creations originating from PSExec and WMI commands". Use WDAC/AppLocker to stop second-stage payloads from running out of %TEMP% and %APPDATA%.
      • IAM and least privilege: Run users without local admin rights so that a sandbox escape yields limited impact. Shorten session-token lifetimes and enable token binding for critical SaaS.
      • Embedded Chromium inventory: Identify Electron apps and kiosk systems that ship their own Chromium engine. Track their vendor advisories separately, because the browser update does not cover them.

    3. Runbook step 3

      Detection rules

      • Vulnerable builds (Defender TVM, KQL): DeviceTvmSoftwareInventory | where SoftwareName has_any ("chrome","edge_chromium") | where SoftwareVersion startswith "120.0." and parse_version(SoftwareVersion) < parse_version("120.0.6099.224"). Substitute the Edge threshold from Microsoft's advisory.
      • Suspicious process ancestry (Sysmon EID 1 / Security 4688): Flag chrome.exe, msedge.exe or opera.exe spawning cmd.exe, powershell.exe, rundll32.exe, mshta.exe, wscript.exe or regsvr32.exe. Sigma shape: ParentImage|endswith: ['\chrome.exe','\msedge.exe'] AND Image|endswith: ['\powershell.exe','\cmd.exe','\rundll32.exe']. Allow-list legitimate native messaging hosts.
      • Renderer crashes as an early signal: Watch Windows Application Event ID 1000/1001 (WER) for chrome.exe/msedge.exe with faulting module chrome.dll/msedge.dll, which can indicate heap corruption. Correlate crash clusters on a host with a shared referrer in proxy logs.
      • File drops by the browser (Sysmon EID 11): Look for .exe, .dll, .ps1 or .hta files written by the browser process outside the Downloads folder, e.g. in %TEMP%, followed by execution within minutes.
      • Network telemetry (Zeek/proxy): Look for first-seen newly registered domains immediately followed by beaconing or new destination ASNs from the same host. Hunt rare SNI values in Zeek ssl.log/http.log that sit close in time to an endpoint process start.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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)

    Source: CSA/SingCERT, pwn.watch, NVD (NIST), cvelistv5, CISA KEV Catalog, CVE.org (MITRE), Debian Security Advisories

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    GoogleChrome
    • < 120.0.6099.224
    • 120.0.6099.224
    couchbasecouchbase_server
    • < 7.2.5
    • 7.2.5
    googlechrome
    • < 120.0.6099.224
    • 120.0.6099.224

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianchromiumbookworm
    Linuxdebianchromiumbullseye
    Otherfedoraprojectfedora38
    Otherfedoraprojectfedora39

    Weakness classes (CWE)

    • CWE-125Out-of-bounds Read

      Base

      The product reads data past the end, or before the beginning, of the intended buffer.

      Entry at MITRE CWE-125

    • CWE-787Out-of-bounds Write

      Base

      The product writes data past the end, or before the beginning, of the intended buffer.

      Entry at MITRE CWE-787

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTActive Exploitation of Zero-Day Vulnerability in Google Chrome (opens in a new tab)CSA/SingCERTactively exploited

    References & sources

    • chromereleases.googleblog.comGoogle advisory: CVE-2024-0519Release notes, pwn-watch
    • crbug.com1517354Permissions required
    • lists.fedoraproject.orgarchives/list/package-announce@lists.fedoraproject.org/message/…Broken link, Mailing list
    • lists.fedoraproject.orgarchives/list/package-announce@lists.fedoraproject.org/message/…Broken link, Mailing list
    • couchbase.comalertsThird-party advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2024-0519government-resource, US government resource
    • pwn.watchpwn.watch: Google Chromium V8 Out-of-Bounds Memory Accesspwn-watch
    • NVD (NIST)NVD: CVE-2024-0519pwn-watch
    • cisa.govCISA Known Exploited Vulnerabilities Catalogpwn-watch
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2024-0519
    <a href="https://intel.neosec.eu/en/cve/CVE-2024-0519"><img src="https://intel.neosec.eu/badge/cve/CVE-2024-0519.svg?lang=en" alt="CVE-2024-0519 – NEOSEC Intel" height="20"></a>