CVE-2024-1283
Google Chrome buffer overflow
- Published6 Feb 2024
Description
Heap buffer overflow in Skia in Google Chrome prior to 121.0.6167.160 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (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/02/stable-channel-update-for-desktop.html
- https://issues.chromium.org/issues/41494860
- https://lists.fedoraproject.org/archives/list/[email protected]/message/KN32XXNHIR6KBS4BYQTZV2JQFN4D6ZSE/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/WSCIL2WH2L4R4KWSRCTDWBPAMOJIYBJE/
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-1283 being actively exploited?
CVE-2024-1283 is not in the CISA KEV catalog. Its EPSS exploit probability is 21.9%.
How severe is CVE-2024-1283?
CVE-2024-1283 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 21.9% probability of exploitation.
Which products are affected by CVE-2024-1283?
Affected products include Google Chrome, Fedoraproject Fedora.
How do I fix CVE-2024-1283?
Upgrade affected software to a fixed version, for example Google Chrome 121.0.6167.160 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-1283 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. 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.