CVE-2022-1483: Heap buffer overflow in WebGPU
Published Apr 8, 2022
·Updated
Heap buffer overflow in WebGPU in Google Chrome prior to 101.0.4951.41 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page.
Credit
Mark Brand(Google Project Zero)
Affected Software
2 affected componentsFixes available
Google Chrome<101.0.4951.41
101.0.4951.41
Google Chrome<101.0.4951.41
Remediation
Patch Available
Event History
Apr 8, 2022
CVE Published
12:00 AM
Jul 26, 2022
CVE Published
via MITRE·09:31 PM
Data Sourced
via MITRE·09:31 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-4919
- CVE-2022-1482
- 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-1483?
CVE-2022-1483 has a severity rating of high due to its potential for remote exploitation.
2
How do I fix CVE-2022-1483?
To fix CVE-2022-1483, update Google Chrome to version 101.0.4951.41 or later.
3
Which versions of Google Chrome are affected by CVE-2022-1483?
Google Chrome versions prior to 101.0.4951.41 are affected by CVE-2022-1483.
4
What type of vulnerability is CVE-2022-1483?
CVE-2022-1483 is classified as a heap buffer overflow vulnerability.
5
Can CVE-2022-1483 be exploited remotely?
Yes, CVE-2022-1483 can be exploited remotely if the attacker compromises the renderer process.