CVE-2022-1499: Inappropriate implementation in WebAuthentication
Published Sep 4, 2019
·Updated
Inappropriate implementation in WebAuthentication in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to bypass same origin policy via a crafted HTML page.
Credit
Jun Kokatsu, Microsoft Browser Vulnerability Research
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
Sep 4, 2019
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-1500
- CVE-2022-1501
Frequently Asked Questions
1
What is the severity of CVE-2022-1499?
CVE-2022-1499 has been classified as a high severity vulnerability in Google Chrome.
2
How do I fix CVE-2022-1499?
To fix CVE-2022-1499, update Google Chrome to version 101.0.4951.41 or later.
3
What does CVE-2022-1499 allow an attacker to do?
CVE-2022-1499 allows a remote attacker to bypass the same origin policy via a crafted HTML page.
4
Which versions of Google Chrome are affected by CVE-2022-1499?
CVE-2022-1499 affects all versions of Google Chrome prior to 101.0.4951.41.
5
Is there any workaround for CVE-2022-1499?
There is no public workaround for CVE-2022-1499; upgrading Chrome is the recommended solution.