CVE-2022-1867: Insufficient validation of untrusted input in Data Transfer
Published Apr 12, 2022
·Updated
Insufficient validation of untrusted input in Data Transfer in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to bypass same origin policy via a crafted clipboard content.
Credit
Michał Bentkowski(Securitum)
Affected Software
2 affected componentsFixes available
Google Chrome<102.0.5005.61
102.0.5005.61
Google Chrome<102.0.5005.61
Event History
Apr 12, 2022
CVE Published
12:00 AM
Jul 27, 2022
CVE Published
via MITRE·09:18 PM
Data Sourced
via MITRE·09:18 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-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-1867?
CVE-2022-1867 is rated as high severity due to its potential to allow remote attackers to bypass security policies.
2
How do I fix CVE-2022-1867?
To fix CVE-2022-1867, update Google Chrome to version 102.0.5005.61 or later.
3
What systems are affected by CVE-2022-1867?
CVE-2022-1867 affects all versions of Google Chrome prior to 102.0.5005.61.
4
What does CVE-2022-1867 exploit?
CVE-2022-1867 exploits insufficient validation of untrusted input in Data Transfer.
5
Can CVE-2022-1867 allow data theft?
Yes, CVE-2022-1867 can allow attackers to potentially steal or manipulate data by bypassing same-origin policy.