Heap buffer overflow in WebRTC in Google Chrome prior to 120.0.6099.129 allowed a remote attacker to potentially exploit heap corruption via
Affects Google Chrome before 120.0.6099.129, where a heap buffer overflow in WebRTC is present. Fixed in Chrome 120.0.6099.129, and Debian ships the fix as 120.0.6099.129-1~deb11u1.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 120.0.6099.129
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Google Chrome's WebRTC component, which handles real-time audio and video communication in the browser, is affected. A remote attacker could create a malicious web page that may corrupt browser memory, potentially allowing them to take control of the affected system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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)
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
Affected versions
- Google Chrome
From 120.0.6099.129 · fixed in 120.0.6099.129
References 6
chromereleases.googleblog.com
crbug.com
debian.org
lists.fedoraproject.org
security.gentoo.org
Questions about CVE-2023-7024
What does this mean?
A heap buffer overflow in WebRTC, Chrome's component for real-time audio and video, can corrupt heap memory. The advisory states that an attacker could execute arbitrary code this way.Source: lists.debian.org
Am I affected, and how do I check?
The description covers Chrome versions prior to 120.0.6099.129. To check a Chrome install, open chrome://settings/help and compare the version shown with that number.Source: lists.debian.org
What should I do about it?
Update Chrome to 120.0.6099.129 or later. On Debian, install the fixed package 120.0.6099.129-1~deb11u1 or a later build.Source: lists.debian.org
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-01-02, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data