CVE-2022-1872: Insufficient policy enforcement in Extensions API
Published Mar 26, 2022
·Updated
Insufficient policy enforcement in Extensions API in Google Chrome prior to 102.0.5005.61 allowed an attacker who convinced a user to install a malicious extension to bypass downloads policy via a crafted HTML page.
Credit
ChaobinZhang
Affected Software
2 affected componentsFixes available
Google Chrome<102.0.5005.61
102.0.5005.61
Google Chrome<102.0.5005.61
Event History
Mar 26, 2022
CVE Published
12:00 AM
Jul 27, 2022
CVE Published
via MITRE·09:19 PM
Data Sourced
via MITRE·09:19 PM
DescriptionWeakness
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-1871
- CVE-2022-1873
- CVE-2022-1874
- CVE-2022-1875
- CVE-2022-1876
Frequently Asked Questions
1
What is the severity of CVE-2022-1872?
CVE-2022-1872 is classified as a medium-severity vulnerability.
2
How do I fix CVE-2022-1872?
To fix CVE-2022-1872, users should update Google Chrome to version 102.0.5005.61 or later.
3
What type of vulnerability is CVE-2022-1872?
CVE-2022-1872 is an insufficient policy enforcement vulnerability in the Extensions API of Google Chrome.
4
Who is affected by CVE-2022-1872?
Users of Google Chrome versions prior to 102.0.5005.61 are affected by CVE-2022-1872.
5
What can an attacker do with CVE-2022-1872?
An attacker can exploit CVE-2022-1872 to bypass the download policy by convincing users to install malicious extensions.