CVE-2022-0117: Policy bypass in Service Workers
Published Aug 13, 2020
·Updated
Policy bypass 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
Dongsung Kim@@kid1ng
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
Remediation
Patch Available
Event History
Aug 13, 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-0113
- CVE-2022-0114
- CVE-2022-0115
- CVE-2022-0116
- CVE-2022-0118
- CVE-2022-0120
- CVE-2022-4925
Frequently Asked Questions
1
What is the severity of CVE-2022-0117?
CVE-2022-0117 is considered a medium severity vulnerability that allows cross-origin data leakage.
2
How do I fix CVE-2022-0117?
To fix CVE-2022-0117, update Google Chrome to version 97.0.4692.71 or later.
3
Who is affected by CVE-2022-0117?
CVE-2022-0117 affects versions of Google Chrome prior to 97.0.4692.71 and specific versions of Chromium on Debian.
4
What causes CVE-2022-0117?
CVE-2022-0117 is caused by a policy bypass in the Blink rendering engine in Google Chrome.
5
How was CVE-2022-0117 discovered?
CVE-2022-0117 was discovered as a result of vulnerability reporting and analysis by security researchers.