CVE-2022-2614: Use after free in Sign-In Flow
Published Jul 5, 2022
·Updated
Use after free in Sign-In Flow in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit
raven at KunLun lab
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
Jul 5, 2022
CVE Published
12:00 AM
Aug 12, 2022
CVE Published
via MITRE·07:36 PM
Data Sourced
via MITRE·07:36 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-4914
- CVE-2022-2615
- CVE-2022-2616
- CVE-2022-2617
- CVE-2022-2618
- 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-2614?
CVE-2022-2614 has a high severity rating due to its potential for remote exploitation leading to heap corruption.
2
How do I fix CVE-2022-2614?
To fix CVE-2022-2614, ensure that Google Chrome is updated to version 104.0.5112.79 or later.
3
What does CVE-2022-2614 affect?
CVE-2022-2614 affects Google Chrome prior to version 104.0.5112.79 and Fedora 37.
4
What is the impact of CVE-2022-2614?
The impact of CVE-2022-2614 could lead to remote code execution due to use after free vulnerabilities.
5
Can CVE-2022-2614 be exploited through web pages?
Yes, CVE-2022-2614 can be exploited via a crafted HTML page by a remote attacker.