CVE-2022-1871: Insufficient policy enforcement in File System API
Insufficient policy enforcement in File System API in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to bypass file system policy via a crafted HTML page.
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-1853
- CVE-2022-1854
- CVE-2022-1855
- CVE-2022-1856
- CVE-2022-1857
- 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-1872
- CVE-2022-1873
- CVE-2022-1874
- CVE-2022-1875
- CVE-2022-1876
Frequently Asked Questions
What is CVE-2022-1871?
CVE-2022-1871 is a vulnerability in Google Chrome that allows an attacker to bypass file system policy via a crafted HTML page.
How severe is CVE-2022-1871?
CVE-2022-1871 has a severity score of 4.3, which is considered medium.
Which version of Google Chrome is affected by CVE-2022-1871?
Google Chrome versions prior to 102.0.5005.61 are affected by CVE-2022-1871.
How can an attacker exploit CVE-2022-1871?
An attacker can exploit CVE-2022-1871 by convincing a user to install a malicious extension and then visiting a crafted HTML page.
Is there a fix for CVE-2022-1871?
Yes, updating Google Chrome to version 102.0.5005.61 or later will fix CVE-2022-1871.