First published: Tue Jan 07 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: chrome-cve-admin@google.com Luan Herrera @lbherrera_
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | <=90.0.4430.212-1~deb10u1 | 116.0.5845.180-1~deb11u1 118.0.5993.70-1~deb11u1 116.0.5845.180-1~deb12u1 118.0.5993.70-1~deb12u1 118.0.5993.70-1 |
Google Chrome (Trace Event) | <97.0.4692.71 | 97.0.4692.71 |
Google Chrome | <97.0.4692.71 | |
Red Hat Fedora | =34 | |
Red Hat Fedora | =35 | |
Red Hat Fedora | =36 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
CVE-2022-0113 has a high severity rating due to its potential to leak cross-origin data.
To fix CVE-2022-0113, update Google Chrome and Chromium to version 97.0.4692.71 or later.
CVE-2022-0113 affects Google Chrome versions prior to 97.0.4692.71 and specific versions of Chromium.
Yes, CVE-2022-0113 can be exploited remotely through a crafted HTML page.
CVE-2022-0113 can lead to unauthorized access to sensitive cross-origin data by attackers.