Security UI bypass via crafted HTML
Published Apr 13, 2020 · Updated Aug 4, 2024
Insufficient omnibox policy enforcement in Google Chrome before 81.0.4044.92 allows remote attackers to bypass security UI via HTML. Google has not publicly disclosed the specific omnibox policy check or the incorrect operation performed on page-controlled input. Exploitation requires a user to open a crafted page, and the documented consequence is limited to bypassing or misleading browser security UI.
Summary
What happened
Insufficient omnibox policy enforcement in Google Chrome before 81.0.4044.92 allows remote attackers to bypass security UI via HTML. Google has not publicly disclosed the specific omnibox policy check or the incorrect operation performed on page-controlled input. Exploitation requires a user to open a crafted page, and the documented consequence is limited to bypassing or misleading browser security UI.
The record
- CVE
- CVE-2020-6441
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-276
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 13, 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 <81.0.4044.92
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