CVE-2022-2618: Insufficient validation of untrusted input in Internals
Published Mar 21, 2022
·Updated
Insufficient validation of untrusted input in Internals in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to bypass download restrictions via a malicious file .
Credit
asnine
Affected Software
3 affected componentsFixes available
Google Chrome<104.0.5112.79
104.0.5112.79
Google Chrome<104.0.5112.79
fedoraproject fedora=37
Event History
Mar 21, 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-2619
- CVE-2022-2620
- CVE-2022-2621
- CVE-2022-2622
- CVE-2022-2623
- CVE-2022-2624
Frequently Asked Questions
1
What is the severity of CVE-2022-2618?
CVE-2022-2618 has a moderate severity rating, indicating it poses a significant risk if exploited.
2
How do I fix CVE-2022-2618?
To fix CVE-2022-2618, users should update Google Chrome to version 104.0.5112.79 or later.
3
What are the effects of CVE-2022-2618?
CVE-2022-2618 can allow remote attackers to bypass download restrictions through malicious files.
4
Is CVE-2022-2618 specific to any operating system?
CVE-2022-2618 affects Google Chrome across multiple operating systems, including Fedora.
5
Can I still be vulnerable to CVE-2022-2618 if I am using an updated version of Chrome?
No, if you are using Google Chrome version 104.0.5112.79 or later, you are not vulnerable to CVE-2022-2618.