CVE-2022-4919: Use after free in Base Internals
Published Apr 1, 2022
·Updated
Use after free in Base Internals in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to perform arbitrary read/write via a crafted HTML page. (Chromium security severity: High)
Credit
Sri
Affected Software
2 affected componentsFixes available
Google Chrome<101.0.4951.41
101.0.4951.41
Google Chrome<101.0.4951.41
Event History
Apr 1, 2022
CVE Published
12:00 AM
Jul 28, 2023
CVE Published
via MITRE·11:26 PM
Data Sourced
via MITRE·11:26 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-1477
- CVE-2022-1478
- CVE-2022-1479
- CVE-2022-4920
- CVE-2022-1481
- CVE-2022-1919
- CVE-2022-1482
- CVE-2022-1483
- CVE-2022-1484
- CVE-2022-1485
- CVE-2022-1486
- CVE-2022-1487
- CVE-2022-1488
- CVE-2022-1489
- CVE-2022-1490
- CVE-2022-1491
- CVE-2022-1492
- CVE-2022-1493
- CVE-2022-1494
- CVE-2022-1495
- CVE-2022-1496
- CVE-2022-1497
- CVE-2022-1498
- CVE-2022-1499
- CVE-2022-1500
- CVE-2022-1501
Frequently Asked Questions
1
What is the severity of CVE-2022-4919?
CVE-2022-4919 has been classified with a High severity level due to the potential for arbitrary read/write by an attacker.
2
How do I fix CVE-2022-4919?
To fix CVE-2022-4919, users should update Google Chrome to version 101.0.4951.41 or later.
3
What does CVE-2022-4919 affect?
CVE-2022-4919 affects Google Chrome versions prior to 101.0.4951.41.
4
What type of vulnerability is CVE-2022-4919?
CVE-2022-4919 is a use after free vulnerability occurring in Base Internals of Google Chrome.
5
Can CVE-2022-4919 be exploited remotely?
Yes, CVE-2022-4919 allows a remote attacker to exploit the vulnerability through a crafted HTML page.