CSP bypass via Trusted Types policy failure
Published Apr 13, 2020 · Updated Aug 4, 2024
Insufficient Trusted Types policy enforcement in Google Chrome before 81.0.4044.92 allows remote attackers to bypass CSP via crafted HTML. Google identifies the locus as Trusted Types policy enforcement but has not published which validation or enforcement operation mishandles the page. The browser must render attacker-controlled HTML on a page relying on Trusted Types CSP; the reported consequence is a policy bypass that defeats script-injection protections.
Summary
What happened
Insufficient Trusted Types policy enforcement in Google Chrome before 81.0.4044.92 allows remote attackers to bypass CSP via crafted HTML. Google identifies the locus as Trusted Types policy enforcement but has not published which validation or enforcement operation mishandles the page. The browser must render attacker-controlled HTML on a page relying on Trusted Types CSP; the reported consequence is a policy bypass that defeats script-injection protections.
The record
- CVE
- CVE-2020-6445
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-276, T1189
- 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.
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