CVE-2022-2619: Insufficient validation of untrusted input in Settings
Published Jun 4, 2022
·Updated
Insufficient validation of untrusted input in Settings in Google Chrome prior to 104.0.5112.79 allowed an attacker who convinced a user to install a malicious extension to inject scripts or HTML into a privileged page via a crafted HTML page.
Credit
Oliver Dunk
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
Jun 4, 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-2620
- CVE-2022-2621
- CVE-2022-2622
- CVE-2022-2623
- CVE-2022-2624
Frequently Asked Questions
1
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2022-2619.
2
What is the severity of CVE-2022-2619?
The severity of CVE-2022-2619 is medium.
3
What software is affected by CVE-2022-2619?
Google Chrome versions prior to 104.0.5112.79 and Fedora 37 are affected by CVE-2022-2619.
4
How can an attacker exploit CVE-2022-2619?
An attacker who convinces a user to install a malicious extension can inject scripts or HTML into a privileged page via a crafted HTML page.
5
How can I fix CVE-2022-2619?
Update Google Chrome to version 104.0.5112.79 or later to fix CVE-2022-2619.