Heap corruption via WebRTC use-after-free
Published Jun 13, 2023 · Updated May 5, 2025
Use after free in Google Chrome WebRTC before 114.0.5735.133 allows remote attackers to corrupt heap memory through crafted HTML. Google has not disclosed the affected WebRTC object, the stale-reference path, or the operation that accesses the freed allocation. A user must load the attacker-controlled page; the public record does not establish whether exploitation stops at a browser crash or achieves code execution.
Summary
What happened
Use after free in Google Chrome WebRTC before 114.0.5735.133 allows remote attackers to corrupt heap memory through crafted HTML. Google has not disclosed the affected WebRTC object, the stale-reference path, or the operation that accesses the freed allocation. A user must load the attacker-controlled page; the public record does not establish whether exploitation stops at a browser crash or achieves code execution.
The record
- CVE
- CVE-2023-3215
- Published
- Jun 13, 2023
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 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.
- Affected versionversion=114.0.5735.133 <114.0.5735.133
What conditions does exploitation require?
What is affected?
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.
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.
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