CVE-2022-3315: Type confusion in Blink
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
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 106.0.5249.61 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 106.0.5249.61-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-3315?
The severity of CVE-2022-3315 is classified as Low by Chromium security standards.
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.
What causes CVE-2022-3315?
CVE-2022-3315 is caused by a type confusion vulnerability in Blink in Google Chrome.
Which versions of Chrome are affected by CVE-2022-3315?
CVE-2022-3315 affects Google Chrome versions prior to 106.0.5249.62.
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.