CVE-2022-3314: Use after free in Logging
Published May 24, 2022
·Updated
Use after free in logging 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
Anonymous
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
May 24, 2022
CVE Published
12:00 AM
Nov 1, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2022-3314?
CVE-2022-3314 has a medium severity level according to Chromium security ratings.
2
How do I fix CVE-2022-3314?
To fix CVE-2022-3314, update Google Chrome to version 106.0.5249.62 or later.
3
Which versions of Chrome are affected by CVE-2022-3314?
CVE-2022-3314 affects all versions of Google Chrome prior to 106.0.5249.62.
4
Can CVE-2022-3314 lead to a sandbox escape?
Yes, CVE-2022-3314 could potentially allow a remote attacker to perform a sandbox escape.
5
Is there a workaround for CVE-2022-3314?
There is no confirmed workaround for CVE-2022-3314, upgrading to a patched version is recommended.