CVE-2022-1487: Use after free in Ozone
Published Mar 9, 2022
·Updated
Use after free in Ozone in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to potentially exploit heap corruption via running a Wayland test.
Credit
Sri
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
Mar 9, 2022
CVE Published
12:00 AM
Jul 26, 2022
CVE Published
via MITRE·09:32 PM
Data Sourced
via MITRE·09:32 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-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-1487?
CVE-2022-1487 has a high severity rating due to its potential for remote exploitation.
2
How do I fix CVE-2022-1487?
To fix CVE-2022-1487, users should update Google Chrome to version 101.0.4951.41 or later.
3
What type of vulnerability is CVE-2022-1487?
CVE-2022-1487 is classified as a use after free vulnerability leading to possible heap corruption.
4
Who is affected by CVE-2022-1487?
Users of Google Chrome versions prior to 101.0.4951.41 are affected by CVE-2022-1487.
5
Can CVE-2022-1487 be exploited remotely?
Yes, CVE-2022-1487 can be exploited remotely by attackers through a specific malicious test.