CVE-2022-1305: Use after free in storage
Use after free in storage in Google Chrome prior to 100.0.4896.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 100.0.4896.88 - Upgrade
Upgrade
alpine/qt5-qtwebengineto a version that resolves this vulnerability.Fixed in 5.15.3_git20211127-r6 - Upgrade
Upgrade
alpine/qt5-qtwebengineto a version that resolves this vulnerability.Fixed in 5.15.3_git20220505-r0 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 100.0.4896.88-1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2022-1305?
CVE-2022-1305 has a high severity rating due to the potential for remote code execution via heap corruption.
How do I fix CVE-2022-1305?
To fix CVE-2022-1305, update Google Chrome to version 100.0.4896.88 or newer.
What versions of Google Chrome are affected by CVE-2022-1305?
CVE-2022-1305 affects Google Chrome versions prior to 100.0.4896.88.
Can CVE-2022-1305 be exploited remotely?
Yes, CVE-2022-1305 can be exploited remotely through a crafted HTML page.
Is there a workaround for CVE-2022-1305?
There is no official workaround for CVE-2022-1305; the best mitigation is to update the browser.