CVE-2022-2622: Insufficient validation of untrusted input in Safe Browsing
Published Jun 3, 2022
·Updated
Insufficient validation of untrusted input in Safe Browsing in Google Chrome on Windows prior to 104.0.5112.79 allowed a remote attacker to bypass download restrictions via a crafted file.
Credit
Imre Rad@@ImreRad, @@j00sean
Affected Software
4 affected componentsFixes available
Google Chrome<104.0.5112.79
104.0.5112.79
Google Chrome<104.0.5112.79
Microsoft Windows
fedoraproject fedora=37
Event History
Jun 3, 2022
CVE Published
12:00 AM
Aug 12, 2022
CVE Published
via MITRE·07:37 PM
Data Sourced
via MITRE·07:37 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-2603
- CVE-2022-2604
- CVE-2022-2605
- CVE-2022-2606
- CVE-2022-2607
- CVE-2022-2608
- CVE-2022-2609
- CVE-2022-2742
- CVE-2022-2743
- CVE-2022-2610
- CVE-2022-2611
- CVE-2022-2612
- CVE-2022-2613
- CVE-2022-2614
- CVE-2022-4914
- CVE-2022-2615
- CVE-2022-2616
- CVE-2022-2617
- CVE-2022-2618
- CVE-2022-2619
- CVE-2022-2620
- CVE-2022-2621
- CVE-2022-2623
- CVE-2022-2624
Frequently Asked Questions
1
What is the severity of CVE-2022-2622?
CVE-2022-2622 is classified as a high severity vulnerability affecting Google Chrome on Windows.
2
How do I fix CVE-2022-2622?
To fix CVE-2022-2622, upgrade Google Chrome to version 104.0.5112.79 or later.
3
What specific issue does CVE-2022-2622 address?
CVE-2022-2622 addresses insufficient validation of untrusted input in Safe Browsing in Google Chrome.
4
Which versions of Google Chrome are affected by CVE-2022-2622?
CVE-2022-2622 affects Google Chrome versions prior to 104.0.5112.79.
5
Can CVE-2022-2622 be exploited remotely?
Yes, CVE-2022-2622 allows a remote attacker to bypass download restrictions through a crafted file.