CVE-2022-1857: Insufficient policy enforcement in File System API
Published Jul 11, 2021
·Updated
Insufficient policy enforcement in File System API in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to bypass file system restrictions via a crafted HTML page.
Credit
Daniel Rhea
Affected Software
2 affected componentsFixes available
Google Chrome<102.0.5005.61
102.0.5005.61
Google Chrome<102.0.5005.61
Event History
Jul 11, 2021
CVE Published
12:00 AM
Jul 27, 2022
CVE Published
via MITRE·09:16 PM
Data Sourced
via MITRE·09:16 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-1853
- CVE-2022-1854
- CVE-2022-1855
- CVE-2022-1856
- CVE-2022-1858
- CVE-2022-1859
- CVE-2022-1860
- CVE-2022-1861
- CVE-2022-1862
- CVE-2022-4918
- CVE-2022-1863
- CVE-2022-1864
- CVE-2022-1865
- CVE-2022-1866
- CVE-2022-1867
- CVE-2022-1868
- CVE-2022-1869
- CVE-2022-1870
- CVE-2022-1871
- CVE-2022-1872
- CVE-2022-1873
- CVE-2022-1874
- CVE-2022-1875
- CVE-2022-1876
Frequently Asked Questions
1
What is the severity of CVE-2022-1857?
CVE-2022-1857 is rated as a high severity vulnerability due to its potential to allow remote attackers to bypass file system restrictions.
2
How do I fix CVE-2022-1857?
To fix CVE-2022-1857, update Google Chrome to version 102.0.5005.61 or later.
3
What types of attacks does CVE-2022-1857 enable?
CVE-2022-1857 enables remote attackers to execute actions that can breach file system restrictions through specially crafted HTML pages.
4
Who is affected by CVE-2022-1857?
Users of Google Chrome versions prior to 102.0.5005.61 are vulnerable to CVE-2022-1857.
5
What systems are impacted by CVE-2022-1857?
CVE-2022-1857 impacts all systems running Google Chrome versions before 102.0.5005.61.