CVE-2022-2623: Use after free in Offline
Published Jun 20, 2022
·Updated
Use after free in Offline in Google Chrome on Android prior to 104.0.5112.79 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via specific UI interactions.
Credit
raven at KunLun lab
Affected Software
4 affected componentsFixes available
Google Chrome<104.0.5112.79
104.0.5112.79
Google Chrome<104.0.5112.79
Google Android
fedoraproject fedora=37
Event History
Jun 20, 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-2622
- CVE-2022-2624
Frequently Asked Questions
1
What is the severity of CVE-2022-2623?
CVE-2022-2623 is considered a high severity vulnerability due to its potential for remote exploitation.
2
How do I fix CVE-2022-2623?
To fix CVE-2022-2623, update Google Chrome to version 104.0.5112.79 or later.
3
What type of vulnerability is CVE-2022-2623?
CVE-2022-2623 is a use-after-free vulnerability that affects the Offline feature in Google Chrome.
4
On which platforms does CVE-2022-2623 affect Google Chrome?
CVE-2022-2623 affects Google Chrome on Android prior to version 104.0.5112.79.
5
Can CVE-2022-2623 be exploited remotely?
Yes, CVE-2022-2623 can be exploited remotely if the user engages in specific UI interactions.