● Not verified · CVSS 0.0 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2024-0519: Out-of-Bounds Memory Access in Google Chrome

Q: Is CVE-2024-0519 being exploited right now?

Yes. It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-01-17), which means CISA has evidence of active exploitation.

Q: What is the CVSS score for CVE-2024-0519?

CVSS 0.0. Use this with your own asset exposure to set patching priority (internet-exposed systems first).

Q: Do I need to take the system offline to patch?

It depends on the platform. Many appliances support hitless upgrade in HA pairs (upgrade standby, fail over, upgrade primary). Servers and applications usually need a service restart. Plan a maintenance window if HA is not available.

Q: What if my version is not listed as affected?

Cross-check against the vendor advisory linked below. The CVE record reflects the vendor's official affected-products list at publication time; later-discovered variants are added through the same advisory or a follow-up CVE.

By Sai Kiran Pandrala

⚡ At a glance


Severity	CVSS 0.0
Actively exploited?	Yes, listed in CISA KEV (added 2024-01-17, federal due date 2024-02-07)
Affected	Chrome: 120.0.6099.224 < version 120.0.6099.224
Fixed in	Chrome: 120.0.6099.224
Type (CWE)	Not verified, see official advisory

What is CVE-2024-0519?

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)

A successful exploit gives the remote attacker the impact described in the vendor advisory. The fix is to install the patched build from Google listed in the table above and confirm the running version after the upgrade.

Am I affected?

Check your installed version of Google Chrome against the Affected row above. If your build sits within any of those ranges, treat the system as vulnerable until patched.

If you do not have the version handy, pull it the same way you usually would for Chrome: the management console's About page, the CLI's version command, or the package manager record for the installed binary. The vendor advisory linked in the references section is the authoritative source.

How to fix CVE-2024-0519

Read the vendor advisory at https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html for the build matrix that matches your installation.
Identify the patched build for your major version: Chrome: 120.0.6099.224.
Back up configuration before upgrading (export running config, snapshot the VM, or take a database dump as appropriate for your platform).
Apply the patched build using the vendor's documented upgrade path (in-place upgrade, package update, or replacement image).
Restart the service so the new code is loaded; verify the running version reports the patched build number.

Patch via your OS package manager


# The exact package name and patched version are listed in the vendor advisory:
# https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html
# Debian / Ubuntu
sudo apt update
sudo apt install --only-upgrade chrome

# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade chrome

# openSUSE
sudo zypper update chrome

# Verify the running version matches the fixed version
dpkg -s chrome 2>/dev/null | grep -i version || rpm -q chrome 2>/dev/null


# Windows: pull the cumulative update that ships this fix.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.html
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2024-0519 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you can't patch immediately

Check the vendor advisory's "Workarounds" section. If the advisory lists no official workaround, patching is the only remediation. Compensating controls that reduce attack surface in the meantime: restrict network access to the management interface to a small admin allowlist, disable the affected feature if it is not in use, and monitor the relevant logs for the exploitation patterns referenced in the advisory.

How to verify the fix worked

Confirm the running version matches the patched build from the vendor advisory.
Re-run your vulnerability scanner; the CVE should clear.
Review logs from before the patch for the exploitation signatures described in the advisory, and treat any matches as a possible compromise (rotate credentials, isolate the host, full IR).

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2024-43093: Security Vulnerability in Google Android — Security Vulnerability in Google Android
How to Fix CVE-2024-22004: Out-of-bounds Read in Nest Wifi Pro — Out-of-bounds Read in Nest Wifi Pro
How to Fix CVE-2024-29745: Information Disclosure in Google Android , Information Disclosure in Google Android
How to Fix CVE-2024-47038: Out-of-bounds Write in Android , Out-of-bounds Write in Android
How to Fix CVE-2024-4761: Out-of-Bounds Memory Access in Google Chrome , Out-of-Bounds Memory Access in Google Chrome

Is CVE-2024-0519 being exploited right now?