Security UI spoofing via crafted HTML page
Published Jun 3, 2020 · Updated Aug 4, 2024
Incorrect security UI in Google Chrome before 80.0.3987.87 allows remote attackers to spoof permission indicators via a crafted HTML page. Google identifies the affected locus only as permissions and has not published the incorrect permission-handling operation. A user must open the crafted page; the resulting deception alters security-relevant UI without reported data disclosure or service interruption.
Summary
What happened
Incorrect security UI in Google Chrome before 80.0.3987.87 allows remote attackers to spoof permission indicators via a crafted HTML page. Google identifies the affected locus only as permissions and has not published the incorrect permission-handling operation. A user must open the crafted page; the resulting deception alters security-relevant UI without reported data disclosure or service interruption.
The record
- CVE
- CVE-2020-6502
- Published
- Jun 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-276, T1036
- 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 <80.0.3987.87
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.
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