CVE-2022-4918: Use after free in UI
Published Apr 11, 2022
·Updated
Use after free in UI in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: Medium)
Credit
Chaoyuan Peng@@ret2happy
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 11, 2022
CVE Published
12:00 AM
Jul 28, 2023
CVE Published
via MITRE·11:26 PM
Data Sourced
via MITRE·11:26 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-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-1875
- CVE-2022-1876
Frequently Asked Questions
1
What is the severity of CVE-2022-4918?
CVE-2022-4918 has a medium severity rating according to Chromium security standards.
2
How do I fix CVE-2022-4918?
To fix CVE-2022-4918, update Google Chrome to version 102.0.5005.61 or later.
3
What are the potential impacts of CVE-2022-4918?
CVE-2022-4918 may allow a remote attacker to perform arbitrary read and write operations via a crafted HTML page.
4
Which versions of Google Chrome are affected by CVE-2022-4918?
CVE-2022-4918 affects all versions of Google Chrome prior to 102.0.5005.61.
5
Is CVE-2022-4918 being actively exploited?
There is no public indication that CVE-2022-4918 is actively being exploited in the wild.