File-system policy bypass via malicious extension
Published Jul 27, 2022 · Updated Aug 3, 2024
Insufficient policy enforcement in Google Chrome before 102.0.5005.61 allows attackers to bypass File System API policy. Google has not published the faulty policy check or the File System API operation that mishandles the crafted HTML page. Exploitation requires a user to install a malicious extension and open attacker-crafted HTML, enabling only the reported file-system policy bypass.
Summary
What happened
Insufficient policy enforcement in Google Chrome before 102.0.5005.61 allows attackers to bypass File System API policy. Google has not published the faulty policy check or the File System API operation that mishandles the crafted HTML page. Exploitation requires a user to install a malicious extension and open attacker-crafted HTML, enabling only the reported file-system policy bypass.
The record
- CVE
- CVE-2022-1871
- Published
- Jul 27, 2022
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1176
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 27, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 <102.0.5005.61
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
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