CVE-2022-3316: Insufficient validation of untrusted input in Safe Browsing
Published Jun 7, 2022
·Updated
Insufficient validation of untrusted input in Safe Browsing in Google Chrome prior to 106.0.5249.62 allowed a remote attacker to bypass security feature via a crafted HTML page. (Chromium security severity: Low)
Credit
Sven Dysthe@@svn_dy
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
Jun 7, 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-3316?
CVE-2022-3316 has a low severity rating according to Chromium security standards.
2
How do I fix CVE-2022-3316?
To fix CVE-2022-3316, update Google Chrome or Chromium to version 106.0.5249.62 or higher.
3
Which versions of Google Chrome are affected by CVE-2022-3316?
CVE-2022-3316 affects Google Chrome versions prior to 106.0.5249.62.
4
Is CVE-2022-3316 a local or remote vulnerability?
CVE-2022-3316 is a remote vulnerability that can be exploited by an attacker via a crafted HTML page.
5
What type of input does CVE-2022-3316 relate to?
CVE-2022-3316 relates to insufficient validation of untrusted input in Safe Browsing features.