CVE-2022-1501: Inappropriate implementation in iframe
Published Feb 2, 2022
·Updated
Inappropriate implementation in iframe in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Credit
Oriol Brufau
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
Feb 2, 2022
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-1500
Frequently Asked Questions
1
What is the severity of CVE-2022-1501?
CVE-2022-1501 has a high severity rating due to its potential for cross-origin data leakage.
2
How do I fix CVE-2022-1501?
To fix CVE-2022-1501, update Google Chrome to version 101.0.4951.41 or later.
3
What types of attacks can CVE-2022-1501 facilitate?
CVE-2022-1501 can facilitate attacks that exploit cross-origin data leakage, potentially compromising sensitive information.
4
Which versions of Google Chrome are affected by CVE-2022-1501?
Google Chrome versions before 101.0.4951.41 are affected by CVE-2022-1501.
5
Who is impacted by CVE-2022-1501?
Any users or organizations utilizing affected versions of Google Chrome are at risk due to CVE-2022-1501.