CVE-2022-0113: Inappropriate implementation in Blink
Published Jan 7, 2020
·Updated
Inappropriate implementation in Blink in Google Chrome prior to 97.0.4692.71 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
Credit
Luan Herrera@@lbherrera_
Affected Software
6 affected componentsFixes available
debian/chromium<=90.0.4430.212-1~deb10u1
116.0.5845.180-1~deb11u1118.0.5993.70-1~deb11u1116.0.5845.180-1~deb12u1118.0.5993.70-1~deb12u1118.0.5993.70-1
Google Chrome<97.0.4692.71
97.0.4692.71
Google Chrome<97.0.4692.71
fedoraproject fedora=34
fedoraproject fedora=35
fedoraproject fedora=36
Event History
Jan 7, 2020
CVE Published
12:00 AM
Feb 11, 2022
CVE Published
via MITRE·11:36 PM
Data Sourced
via MITRE·11:36 PM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-0096
- CVE-2022-0097
- CVE-2022-0098
- CVE-2022-0099
- CVE-2022-0100
- CVE-2022-0101
- CVE-2022-0337
- CVE-2022-0102
- CVE-2022-0103
- CVE-2022-4924
- CVE-2022-0104
- CVE-2022-0105
- CVE-2022-0106
- CVE-2022-0107
- CVE-2022-0108
- CVE-2022-0109
- CVE-2022-0110
- CVE-2022-0111
- CVE-2022-0112
- CVE-2022-0114
- CVE-2022-0115
- CVE-2022-0116
- CVE-2022-0117
- CVE-2022-0118
- CVE-2022-0120
- CVE-2022-4925
Frequently Asked Questions
1
What is the severity of CVE-2022-0113?
CVE-2022-0113 has a high severity rating due to its potential to leak cross-origin data.
2
How do I fix CVE-2022-0113?
To fix CVE-2022-0113, update Google Chrome and Chromium to version 97.0.4692.71 or later.
3
Which software is affected by CVE-2022-0113?
CVE-2022-0113 affects Google Chrome versions prior to 97.0.4692.71 and specific versions of Chromium.
4
Can CVE-2022-0113 be exploited remotely?
Yes, CVE-2022-0113 can be exploited remotely through a crafted HTML page.
5
What impact does CVE-2022-0113 have on users?
CVE-2022-0113 can lead to unauthorized access to sensitive cross-origin data by attackers.