Security readout for executives and security teams
Plain-English summary
CVE-2024-0519 is a Chrome V8 memory-safety flaw triggerable through a crafted HTML page. Successful exploitation could compromise browser confidentiality, integrity, and availability. Because CISA lists it in KEV, outdated Chrome installations should be treated as an urgent exposure.
Executive priority
Treat this as urgent because exploitation is known and the impact can include full browser compromise. Remediation is straightforward: identify outdated browsers and force updates quickly.
Technical view
The CVE describes out-of-bounds memory access in V8 before Google Chrome 120.0.6099.224, potentially leading to heap corruption. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required.
Likely exposure
Primary exposure is desktop Chrome versions before 120.0.6099.224. Organizations should also consider managed endpoints, unmanaged user devices, and downstream Chromium package channels referenced by vendor advisories.
Exploitation context
Active exploitation is supported by CISA KEV status. The source bundle describes exploitation via a crafted HTML page, requiring user interaction but no privileges. No weaponized details are provided here.
Researcher notes
Evidence supports a high-severity V8 memory corruption class issue with CWE-125 and CWE-787 mappings. Public details in the bundle are limited; avoid assuming exploit mechanics beyond crafted HTML and heap corruption.
Mitigation direction
- Update Chrome to 120.0.6099.224 or later.
- Prioritize managed and unmanaged desktop browser remediation.
- Review vendor advisories for downstream Chromium package updates.
- Confirm browser auto-update enforcement through endpoint management.
- Check referenced vendor guidance before applying non-Google mitigations.
Validation and detection
- Inventory Chrome versions across managed endpoints.
- Flag any Chrome version earlier than 120.0.6099.224.
- Verify update policies are enabled and effective.
- Review CISA KEV tracking for remediation deadlines.
- Check relevant Fedora or vendor advisories if using packaged Chromium.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-0519 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_16.htmlCVE reference
- https://crbug.com/1517354CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IIUBRVICICWREJQUVT67RS7E4PVZQ5RS/CVE reference
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNN4SO5UI3U3Q6ASTVT6WMZ4723FYDLH/CVE reference
- https://www.couchbase.com/alerts/CVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-0519CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.