CVE-2022-1853: Use after free in Indexed DB
Published May 12, 2022
·Updated
Use after free in Indexed DB in Google Chrome prior to 102.0.5005.61 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.
Credit
Anonymous
Affected Software
2 affected componentsFixes available
Google Chrome<102.0.5005.61
102.0.5005.61
Google Chrome<102.0.5005.61
Event History
May 12, 2022
CVE Published
12:00 AM
Jul 27, 2022
CVE Published
via MITRE·09:15 PM
Data Sourced
via MITRE·09:15 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- 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-1875
- CVE-2022-1876
Frequently Asked Questions
1
What is the severity of CVE-2022-1853?
The severity of CVE-2022-1853 is considered high due to its potential for sandbox escape.
2
How do I fix CVE-2022-1853?
To fix CVE-2022-1853, update Google Chrome to version 102.0.5005.61 or later.
3
What does CVE-2022-1853 affect?
CVE-2022-1853 affects Google Chrome versions prior to 102.0.5005.61.
4
What type of vulnerability is CVE-2022-1853?
CVE-2022-1853 is a use after free vulnerability in Indexed DB.
5
Can CVE-2022-1853 be exploited remotely?
Yes, CVE-2022-1853 can potentially be exploited remotely via a crafted HTML page.