Heap corruption via uninitialized WebRTC data
Published Apr 13, 2020 · Updated Aug 4, 2024
Uninitialized use in Google Chrome's WebRTC component before 81.0.4044.92 allows remote attackers to corrupt heap memory through crafted HTML. The public record identifies WebRTC as the locus but does not disclose the affected function, object, or code path that consumes uninitialized data. A victim must load attacker-controlled HTML; resulting memory corruption can affect confidentiality, integrity, and availability, but no code-execution outcome is documented.
Summary
What happened
Uninitialized use in Google Chrome's WebRTC component before 81.0.4044.92 allows remote attackers to corrupt heap memory through crafted HTML. The public record identifies WebRTC as the locus but does not disclose the affected function, object, or code path that consumes uninitialized data. A victim must load attacker-controlled HTML; resulting memory corruption can affect confidentiality, integrity, and availability, but no code-execution outcome is documented.
The record
- CVE
- CVE-2020-6444
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-908, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 <81.0.4044.92
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.
Weakness, pattern, technique
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