CVE-2024-0808
Google Chrome integer overflow
- Published23 Jan 2024
Description
Integer underflow in WebUI in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://chromereleases.googleblog.com/2024/01/stable-channel-update-for-desktop_23.html
- https://crbug.com/1504936
- https://lists.fedoraproject.org/archives/list/[email protected]/message/MMI6GXFONZV6HE3BPZO3AP6GUVQLG4JQ/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/VXDSGAFQD4BDB4IB2O4ZUSHC3JCVQEKC/
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-0808 being actively exploited?
CVE-2024-0808 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.55%.
How severe is CVE-2024-0808?
CVE-2024-0808 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.55% probability of exploitation.
Which products are affected by CVE-2024-0808?
Affected products include Google Chrome, Debian Linux, Fedoraproject Fedora.
How do I fix CVE-2024-0808?
Upgrade affected software to a fixed version, for example Google Chrome 121.0.6167.85 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-0808 against the real software inventory on every managed device, every day. 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. 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.