Omnibox spoofing via crafted payment page
Published Jun 3, 2020 · Updated Aug 4, 2024
Incorrect security UI in Google Chrome for Android before 83.0.4103.97 allows remote attackers to spoof the Omnibox via crafted HTML. Google identifies payment handling as the affected locus but has not disclosed which incorrect operation lets attacker-controlled page content falsify the displayed URL. A user must open and interact with the crafted page; the false origin display can mislead navigation decisions but does not itself grant data access or code execution.
Summary
What happened
Incorrect security UI in Google Chrome for Android before 83.0.4103.97 allows remote attackers to spoof the Omnibox via crafted HTML. Google identifies payment handling as the affected locus but has not disclosed which incorrect operation lets attacker-controlled page content falsify the displayed URL. A user must open and interact with the crafted page; the false origin display can mislead navigation decisions but does not itself grant data access or code execution.
The record
- CVE
- CVE-2020-6494
- Published
- Jun 3, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- 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 <83.0.4103.97
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
No sourced classifications are available.
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