CVE-2024-4761
Google Chromium V8 Out-of-Bounds Memory Write
- Published14 May 2024
- Added to CISA KEV16 May 2024
- Remediation due6 Jun 2024
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)
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html
- https://issues.chromium.org/issues/339458194
- https://lists.fedoraproject.org/archives/list/[email protected]/message/6G7EYH2JAK5OJPVNC6AXYQ5K7YGYNCDN/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/NTSN22LNYXMWHVTYNOYQVOY7VDZFHENQ/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/WSUWM73ZCXTN62AT2REYQDD5ZKPFMDZD/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-4761
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-4761 being actively exploited?
Yes. CVE-2024-4761 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 16 May 2024.
How severe is CVE-2024-4761?
CVE-2024-4761 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 11.0% probability of exploitation.
Which products are affected by CVE-2024-4761?
Affected products include Google Chrome, Fedoraproject Fedora.
How do I fix CVE-2024-4761?
Upgrade affected software to a fixed version, for example Google Chrome 124.0.6367.207 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-4761 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.