Content security policy bypass via crafted HTML
Published Feb 11, 2020 · Updated Aug 4, 2024
Input validation failure in Blink in Google Chrome before 80.0.3987.87 allows local users to bypass content security policy via crafted HTML. Google's public advisory identifies insufficient validation of crafted HTML but does not disclose the Blink function or exact validation operation that accepts it. Execution requires user interaction with attacker-controlled HTML; the bypass weakens page content restrictions without reported confidentiality or availability impact.
Summary
What happened
Input validation failure in Blink in Google Chrome before 80.0.3987.87 allows local users to bypass content security policy via crafted HTML. Google's public advisory identifies insufficient validation of crafted HTML but does not disclose the Blink function or exact validation operation that accepts it. Execution requires user interaction with attacker-controlled HTML; the bypass weakens page content restrictions without reported confidentiality or availability impact.
The record
- CVE
- CVE-2020-6391
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-79, T1204
- Attack vector
- local
- Privileges
- Unavailable
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?
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