Code execution via WebRTC memory reuse
Published Aug 26, 2021 · Updated Aug 3, 2024
Use after free in WebRTC in Google Chrome before 92.0.4515.159 allows remote attackers to execute arbitrary code via crafted HTML. TrackAddIceCandidate accesses an ICE candidate after setLocalDescription and garbage collection mark its backing memory for reuse. A user must visit a malicious website; controlled reuse of the freed memory enables code execution in the Chrome process.
Summary
What happened
Use after free in WebRTC in Google Chrome before 92.0.4515.159 allows remote attackers to execute arbitrary code via crafted HTML. TrackAddIceCandidate accesses an ICE candidate after setLocalDescription and garbage collection mark its backing memory for reuse. A user must visit a malicious website; controlled reuse of the freed memory enables code execution in the Chrome process.
The record
- CVE
- CVE-2021-30602
- Published
- Aug 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <92.0.4515.159
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
- Cisco Talos WebRTC addIceCandidate proof of conceptproof of concept · demonstrated
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