CVE-2022-2857: Use after free in Blink
Use after free in Blink in Google Chrome prior to 104.0.5112.101 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 104.0.5112.101 - 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.47-1Fixed in 156.0.8078.79-1 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 104.0.5112.101-1
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2022-2857?
CVE-2022-2857 is classified as a high severity vulnerability due to its potential to exploit heap corruption in Google Chrome.
How do I fix CVE-2022-2857?
To fix CVE-2022-2857, update Google Chrome to version 104.0.5112.101 or later.
Which versions of Google Chrome are affected by CVE-2022-2857?
CVE-2022-2857 affects all versions of Google Chrome prior to 104.0.5112.101.
Is there a workaround for CVE-2022-2857?
There are no known workarounds for CVE-2022-2857, and the best course of action is to apply the software update.
Can CVE-2022-2857 be exploited remotely?
Yes, CVE-2022-2857 allows a remote attacker to potentially exploit the vulnerability via a carefully crafted HTML page.