Filesystem restriction bypass via unsafe picker extensions
Published Feb 9, 2021 · Updated Aug 3, 2024
Insufficient policy enforcement in Chrome's File System API before 88.0.4324.96 allows remote attackers to bypass file restrictions via crafted HTML. The file-picker validation accepts unsafe extension strings and passes them to open or save dialogs instead of rejecting invalid characters, excessive lengths, trailing dots, or .local and .lnk endings. The attack requires a user to open the page and interact with a file picker, and the published consequence is limited to a filesystem-policy bypass.
Summary
What happened
Insufficient policy enforcement in Chrome's File System API before 88.0.4324.96 allows remote attackers to bypass file restrictions via crafted HTML. The file-picker validation accepts unsafe extension strings and passes them to open or save dialogs instead of rejecting invalid characters, excessive lengths, trailing dots, or .local and .lnk endings. The attack requires a user to open the page and interact with a file picker, and the published consequence is limited to a filesystem-policy bypass.
The record
- CVE
- CVE-2021-21130
- Published
- Feb 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2021CVE 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 <88.0.4324.96
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