Heap corruption via WebRTC use-after-free
Published Oct 29, 2024 · Updated Oct 31, 2024
Use-after-free in WebRTC in Google Chrome before 130.0.6723.92 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the defect as use-after-free memory access in WebRTC, but the restricted bug record does not disclose the affected function or object-lifetime error. A user must load attacker-controlled HTML; successful exploitation then compromises browser confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in WebRTC in Google Chrome before 130.0.6723.92 allows remote attackers to corrupt heap memory via a crafted HTML page. Google identifies the defect as use-after-free memory access in WebRTC, but the restricted bug record does not disclose the affected function or object-lifetime error. A user must load attacker-controlled HTML; successful exploitation then compromises browser confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-10488
- Published
- Oct 29, 2024
- Updated
- Oct 31, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2024CVE publishedPublication date reported by the CVE source.
- Oct 31, 2024Record 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=0 <130.0.6723.92
- Affected versionversion=130.0.6723.92 <130.0.6723.92
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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