Site isolation bypass via malicious extension
Published Mar 23, 2020 · Updated Aug 4, 2024
Insufficient policy enforcement in Google Chrome before 80.0.3987.149 allows attackers to bypass site isolation via a crafted extension. Google has not published the affected extension-policy locus or the incorrect policy decision that accepts the crafted extension. Exploitation requires a user to install the malicious extension, after which the bypass weakens the browser's cross-site process boundary and permits limited data disclosure or modification.
Summary
What happened
Insufficient policy enforcement in Google Chrome before 80.0.3987.149 allows attackers to bypass site isolation via a crafted extension. Google has not published the affected extension-policy locus or the incorrect policy decision that accepts the crafted extension. Exploitation requires a user to install the malicious extension, after which the bypass weakens the browser's cross-site process boundary and permits limited data disclosure or modification.
The record
- CVE
- CVE-2020-6425
- Published
- Mar 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-20, T1176
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 23, 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.149
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.
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