Remote heap corruption via crafted HTML page
Published Jan 14, 2020 · Updated Aug 5, 2024
Inappropriate implementation in WebRTC in Google Chrome before 79.0.3945.79 allows remote attackers to trigger heap corruption via a crafted HTML page. Public records do not identify the WebRTC locus or faulty operation beyond describing an inappropriate implementation reached by crafted HTML. A victim must load attacker-controlled HTML; resulting corruption can crash the browser process, while code-execution impact is not established.
Summary
What happened
Inappropriate implementation in WebRTC in Google Chrome before 79.0.3945.79 allows remote attackers to trigger heap corruption via a crafted HTML page. Public records do not identify the WebRTC locus or faulty operation beyond describing an inappropriate implementation reached by crafted HTML. A victim must load attacker-controlled HTML; resulting corruption can crash the browser process, while code-execution impact is not established.
The record
- CVE
- CVE-2019-13722
- Published
- Jan 14, 2020
- Updated
- Aug 5, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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 <79.0.3945.79
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.
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