Process-memory disclosure via crafted HTML page
Published Jun 3, 2020 · Updated Aug 4, 2024
Information disclosure in Google Chrome before 74.0.3729.108 allows remote attackers to read process memory via a crafted HTML page. Google identifies the locus only as its accessibility implementation and has not published the incorrect operation performed on page-controlled input. Exploitation requires a user to open the crafted page; the reported consequence is memory disclosure without integrity or availability impact.
Summary
What happened
Information disclosure in Google Chrome before 74.0.3729.108 allows remote attackers to read process memory via a crafted HTML page. Google identifies the locus only as its accessibility implementation and has not published the incorrect operation performed on page-controlled input. Exploitation requires a user to open the crafted page; the reported consequence is memory disclosure without integrity or availability impact.
The record
- CVE
- CVE-2020-6503
- Published
- Jun 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-209, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 3, 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 <74.0.3729.108
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