Navigation restriction bypass via crafted domain name
Published Feb 11, 2020 · Updated Aug 4, 2024
Navigation restriction bypass in Google Chrome before 80.0.3987.87 allows remote attackers to evade restrictions via a crafted domain name. The Omnibox mishandles the crafted domain name in a user-entered URI, but Google has not disclosed the responsible function or validation error. Exploitation requires convincing a user to enter the URI and is bounded to navigation-policy bypass; no code execution or data access is reported.
Summary
What happened
Navigation restriction bypass in Google Chrome before 80.0.3987.87 allows remote attackers to evade restrictions via a crafted domain name. The Omnibox mishandles the crafted domain name in a user-entered URI, but Google has not disclosed the responsible function or validation error. Exploitation requires convincing a user to enter the URI and is bounded to navigation-policy bypass; no code execution or data access is reported.
The record
- CVE
- CVE-2020-6409
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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