Process-memory disclosure to remote attackers
Published May 21, 2020 · Updated Aug 4, 2024
Information disclosure in Blink in Google Chrome before 83.0.4103.61 allows remote attackers to read process memory via crafted HTML. Google identifies insufficient policy enforcement in Blink, but the public advisory does not disclose the affected policy check or the operation that exposes memory. Exploitation requires a user to open attacker-controlled HTML; the documented consequence is process-memory disclosure without data modification or service interruption.
Summary
What happened
Information disclosure in Blink in Google Chrome before 83.0.4103.61 allows remote attackers to read process memory via crafted HTML. Google identifies insufficient policy enforcement in Blink, but the public advisory does not disclose the affected policy check or the operation that exposes memory. Exploitation requires a user to open attacker-controlled HTML; the documented consequence is process-memory disclosure without data modification or service interruption.
The record
- CVE
- CVE-2020-6473
- Published
- May 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-203, CAPEC-189, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 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 <83.0.4103.61
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