CVE-2022-3311: Use after free in Import
Published Mar 4, 2022
·Updated
Use after free in import in Google Chrome prior to 106.0.5249.62 allowed a remote attacker who had compromised a WebUI process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
Credit
Samet Bekmezci@@sametbekmezci
Affected Software
3 affected componentsFixes available
debian/chromium<=90.0.4430.212-1~deb10u1
116.0.5845.180-1~deb11u1120.0.6099.109-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.109-1~deb12u1120.0.6099.109-1
Google Chrome<106.0.5249.61
106.0.5249.61
Google Chrome<106.0.5249.62
Event History
Mar 4, 2022
CVE Published
12:00 AM
Nov 1, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2022-3311?
CVE-2022-3311 has a medium severity rating in terms of Chromium security.
2
How do I fix CVE-2022-3311?
To fix CVE-2022-3311, update Google Chrome to version 106.0.5249.62 or later.
3
Which versions of Google Chrome are affected by CVE-2022-3311?
CVE-2022-3311 affects Google Chrome versions up to and including 106.0.5249.61.
4
Can CVE-2022-3311 lead to a sandbox escape?
Yes, CVE-2022-3311 allows remote attackers to potentially perform a sandbox escape via a crafted HTML page.
5
Is there a workaround for CVE-2022-3311?
The recommended solution for CVE-2022-3311 is to update to the latest version of Google Chrome, as there are no known workarounds.