CVE-2022-2857: Use after free in Blink
Published Jun 21, 2022
·Updated
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
Anonymous
Affected Software
3 affected componentsFixes available
Google Chrome<104.0.5112.101
104.0.5112.101
Google Chrome<104.0.5112.101
fedoraproject fedora=37
Remediation
Event History
Jun 21, 2022
CVE Published
12:00 AM
Sep 26, 2022
CVE Published
via MITRE·03:01 PM
Data Sourced
via MITRE·03:01 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
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.
2
How do I fix CVE-2022-2857?
To fix CVE-2022-2857, update Google Chrome to version 104.0.5112.101 or later.
3
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.
4
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.
5
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.