Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2023-7024

Google Chromium WebRTC Heap Buffer Overflow Vulnerability

Google Chromium WebRTC

Heap buffer overflow in WebRTC in Google Chrome prior to 120.0.6099.129 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS
8.8
HIGH
EPSS
6.7%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
21 Dec 2023
CWE-787

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 2 January 2024. US federal agencies were required to remediate it by 23 January 2024.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 6.7%, which is higher than 93.8% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2023-7024 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2023-7024.

What does CVE-2023-7024 affect?

CVE-2023-7024 affects Google Chromium WebRTC. Heap buffer overflow in WebRTC in Google Chrome prior to 120.0.6099.129 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

How severe is CVE-2023-7024?

CVE-2023-7024 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 6.7%, higher than 93.8% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 23 January 2024.

How should organisations respond to CVE-2023-7024?

Apply the vendor patch for Google Chromium WebRTC as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.