First published: Tue Jun 07 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: chrome-cve-admin@google.com Sven Dysthe @svn_dy
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | <=90.0.4430.212-1~deb10u1 | 116.0.5845.180-1~deb11u1 120.0.6099.109-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.109-1~deb12u1 120.0.6099.109-1 |
Google Chrome (Trace Event) | <106.0.5249.61 | 106.0.5249.61 |
Google Chrome (Trace Event) | <106.0.5249.62 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2022-3316 has a low severity rating according to Chromium security standards.
To fix CVE-2022-3316, update Google Chrome or Chromium to version 106.0.5249.62 or higher.
CVE-2022-3316 affects Google Chrome versions prior to 106.0.5249.62.
CVE-2022-3316 is a remote vulnerability that can be exploited by an attacker via a crafted HTML page.
CVE-2022-3316 relates to insufficient validation of untrusted input in Safe Browsing features.