CVE-2022-1500: Insufficient data validation in Dev Tools
Published Jun 25, 2021
·Updated
Insufficient data validation in Dev Tools in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to bypass content security policy via a crafted HTML page.
Credit
Hoang Nguyen
Affected Software
2 affected componentsFixes available
Google Chrome<101.0.4951.41
101.0.4951.41
Google Chrome<101.0.4951.41
Event History
Jun 25, 2021
CVE Published
12:00 AM
Jul 26, 2022
CVE Published
via MITRE·09:35 PM
Data Sourced
via MITRE·09:35 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-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-1501
Frequently Asked Questions
1
What is the severity of CVE-2022-1500?
The severity of CVE-2022-1500 is considered high due to the potential for a remote attacker to bypass content security policy.
2
How do I fix CVE-2022-1500?
To fix CVE-2022-1500, update Google Chrome to version 101.0.4951.41 or later.
3
What kind of attack can exploit CVE-2022-1500?
CVE-2022-1500 can be exploited through a crafted HTML page that circumvents the content security policy.
4
Which versions of Google Chrome are affected by CVE-2022-1500?
Google Chrome versions prior to 101.0.4951.41 are affected by CVE-2022-1500.
5
Are there any workarounds for CVE-2022-1500?
No specific workarounds for CVE-2022-1500 are available; updating to the latest version is recommended.