CVE-2024-0519

Exp

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)

Published: 2024-01-16 Last update: 2025-10-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-0519 is rated Critical Active Threat (94.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.77%). CISA KEV confirms active exploitation (added 2024-01-17) affecting Google / Chromium V8. a weakness (CWE-125) Unauthenticated remote administrative access may be possible. EPSS rose +3.59% over the last day, indicating growing attacker interest. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2024-0519

Name: Google Chromium V8 Out-of-Bounds Memory Access Vulnerability · CISA KEV detail

Exploit added: 2024-01-17

Action due: 2024-02-07

Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Exploit prediction scoring system (EPSS) score for CVE-2024-0519

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.18% 3.77% +3.59%
2 2026-06-07 0.13% 0.18% +0.04%
3 2026-06-05 — 0.13% —

Full EPSS history (41 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-0519

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-0519

OS Trackers for CVE-2024-0519

vendor priority summary link
alpine — CVE-2024-0519: 2 source package rows (qt5-qtwebengine, qt6-qtwebengine); 10 state rows across 5 repos (3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2024-0519
debian not yet assigned CVE-2024-0519 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-0519
gentoo high CVE-2024-0519: 2 GLSA(s) (202402-14, 202402-23), 4 atom(s) (dev-qt/qtwebengine, www-client/chromium, www-client/google-chrome, www-client/microsoft-edge); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-0519
ubuntu medium CVE-2024-0519 medium priority: Ubuntu including 1 source packages (chromium-browser), 8 status rows across 8 suites (bionic, focal, jammy, lunar, mantic, trusty, upstream, xenial): ignored 3, not-affected 3, DNE 1, released 1. https://ubuntu.com/security/CVE-2024-0519

Affected software / configurations for CVE-2024-0519

Vendor Product Version Raw CPE
google chrome < 120.0.6099.224 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
fedoraproject fedora 38 cpe:2.3:o:fedoraproject:fedora:38:*:*:*:*:*:*:*
fedoraproject fedora 39 cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*
couchbase couchbase_server < 7.2.5 cpe:2.3:a:couchbase:couchbase_server:*:*:*:*:*:*:*:*

References for CVE-2024-0519

cvelogic Threat Intelligence