CVE-2022-3315: Type confusion in Blink
Published May 5, 2022
·Updated
Type confusion in Blink in Google Chrome prior to 106.0.5249.62 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Low)
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 5, 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-3315?
The severity of CVE-2022-3315 is classified as Low by Chromium security standards.
2
How do I fix CVE-2022-3315?
To fix CVE-2022-3315, update Google Chrome or Chromium to at least version 106.0.5249.62.
3
What causes CVE-2022-3315?
CVE-2022-3315 is caused by a type confusion vulnerability in Blink in Google Chrome.
4
Which versions of Chrome are affected by CVE-2022-3315?
CVE-2022-3315 affects Google Chrome versions prior to 106.0.5249.62.
5
Can CVE-2022-3315 lead to remote code execution?
CVE-2022-3315 may potentially allow a remote attacker to exploit heap corruption, but it does not guarantee remote code execution.