CVE-2022-1875: Inappropriate implementation in PDF
Published Mar 15, 2022
·Updated
Inappropriate implementation in PDF in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Credit
NDevTK
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 15, 2022
CVE Published
12:00 AM
Jul 27, 2022
CVE Published
via MITRE·09:20 PM
Data Sourced
via MITRE·09:20 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-1872
- CVE-2022-1873
- CVE-2022-1874
- CVE-2022-1876
Frequently Asked Questions
1
What is the severity of CVE-2022-1875?
CVE-2022-1875 is categorized as a high-severity vulnerability.
2
How do I fix CVE-2022-1875?
To fix CVE-2022-1875, update Google Chrome to version 102.0.5005.61 or later.
3
What type of attack does CVE-2022-1875 enable?
CVE-2022-1875 allows a remote attacker to leak cross-origin data.
4
Who is affected by CVE-2022-1875?
Users of Google Chrome versions prior to 102.0.5005.61 are affected by CVE-2022-1875.
5
What was the cause of CVE-2022-1875?
CVE-2022-1875 was caused by an inappropriate implementation in the PDF handling feature of Google Chrome.