Live › vulnerability › CVE-2023-7024
Go to dashboardA heap buffer overflow in the WebRTC component of Chromium lets a remote attacker corrupt heap memory by getting a victim to load a crafted HTML page. Exploitation in the wild is confirmed by CISA's KEV catalog.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC, 3h before NVD. All times on this page are UTC.
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Google Chromium WebRTC | vendor | – | – |
| google chrome | vendor | < 120.0.6099.129 | 120.0.6099.129 |
| debian linux | vendor | = 11.0 | – |
| debian linux | vendor | = 12.0 | – |
| fedoraproject fedora | vendor | = 38 | – |
| fedoraproject fedora | vendor | = 39 | – |
Unknown from the sources.
Update Google Chrome and other Chromium-based browsers to a release that includes the vendor's fix; the sources do not name the fixed version.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Google Chromium WebRTC, an open-source project providing web browsers with real-time communication, contains a heap buffer overflow vulnerability that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could impact web browsers using WebRTC, including but not limited to Google Chrome.
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
This page as .md · .json · in your agent: get_signal("CVE-2023-7024")
CISA KEV catalog, Creative Commons 0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.