CVE-2022-1869: Type Confusion in V8
Published Mar 23, 2022
·Updated
Type Confusion in V8 in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit
Man Yue Mo(GitHub Security Lab)
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 23, 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-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-1869?
CVE-2022-1869 is classified as a high-severity vulnerability due to the potential for remote code execution from heap corruption.
2
How do I fix CVE-2022-1869?
To mitigate CVE-2022-1869, update Google Chrome to version 102.0.5005.61 or later.
3
What systems are affected by CVE-2022-1869?
CVE-2022-1869 affects all versions of Google Chrome prior to 102.0.5005.61 on desktop platforms.
4
What type of vulnerability is CVE-2022-1869?
CVE-2022-1869 is a type confusion vulnerability found in the V8 JavaScript engine of Google Chrome.
5
Can CVE-2022-1869 be exploited by attackers?
Yes, CVE-2022-1869 can potentially be exploited by attackers through crafted HTML pages, leading to serious security risks.