CVE-2023-7024Known exploitationNetwork attack vector

Code execution via WebRTC heap overflow

Published Dec 21, 2023 · Updated Oct 21, 2025

Heap buffer overflow in WebRTC in Google Chrome before 120.0.6099.129 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the affected locus only as WebRTC and has not disclosed the specific buffer operation or input field that writes beyond its heap allocation. Exploitation requires a user to load attacker-controlled HTML, and successful corruption can execute code in the logged-on-user context or crash Chrome.

CVSS severity8.8
High
EPSS probability7.36%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap buffer overflow in WebRTC in Google Chrome before 120.0.6099.129 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the affected locus only as WebRTC and has not disclosed the specific buffer operation or input field that writes beyond its heap allocation. Exploitation requires a user to load attacker-controlled HTML, and successful corruption can execute code in the logged-on-user context or crash Chrome.

The record

CVE
CVE-2023-7024
Published
Dec 21, 2023
Updated
Oct 21, 2025
Vendor
Google Cloud
Product
Google Chrome
Classifications
CWE-787, T1203, T1189
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 21, 2023CVE publishedPublication date reported by the CVE source.
  2. Jan 2, 2024Exploitation reportedCISA Known Exploited Vulnerabilities Catalog entry
  3. Oct 21, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=120.0.6099.129 <120.0.6099.129

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Google Cloud · Google Chromeversion=120.0.6099.129 <120.0.6099.129

Published CVSS scores

8.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
8.8NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write
T1203Exploitation for Client Execution
T1189Drive-by Compromise

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Reported exploitation

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo