CVE-2023-7024highunder attackCWE-787

CVE-2023-7024: high-severity vulnerability in Google Chrome

Published · Updated

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

71Vexday Risk Score

Prioritize patching. It under exploitation confirmed by CISA and has a public proof of concept.

ssvc Actcvss 8.8epss 6.7%
from disclosure to weapon687 days
Published on NVDDec 21
1st PoC+687d
CISA KEV+12d
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Not affected
1 product — because the vulnerable code is not present in the product
red_hat_products
Action required by CISAfederal deadline: 2024-01-23

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

In short

A flaw in Google Chrome's WebRTC feature allows attackers to corrupt memory through a specially crafted webpage, potentially crashing your browser or enabling more serious attacks.

Technical detail

Heap buffer overflow in WebRTC component allows remote code execution or denial of service via crafted HTML. Attack requires user interaction (visiting malicious page); impacts memory integrity and sandbox bypass potential.

Summary generated and translated by AI from the official description.

The full analysis of this CVE is available in Portuguese →

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:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
Google · Chrome
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.