CVE-2022-4182: Inappropriate implementation in Fenced Frames
Published Sep 28, 2022
·Updated
Inappropriate implementation in Fenced Frames in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to bypass fenced frame restrictions via a crafted HTML page. (Chromium security severity: Medium)
Credit
Peter Nemeth
Affected Software
2 affected componentsFixes available
Google Chrome<108.0.5359.71
108.0.5359.71
Google Chrome<108.0.5359.71
Event History
Sep 28, 2022
CVE Published
12:00 AM
Nov 29, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Nov 30, 2022
Data Sourced
via NVD·12:15 AM
DescriptionSeverityAffected Software
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2022-4174
- CVE-2022-4175
- CVE-2022-4176
- CVE-2022-4177
- CVE-2022-4178
- CVE-2022-4179
- CVE-2022-4180
- CVE-2022-4906
- CVE-2022-4181
- CVE-2022-4907
- CVE-2022-4955
- CVE-2022-4183
- CVE-2022-4184
- CVE-2022-4185
- CVE-2022-4186
- CVE-2022-4187
- CVE-2022-4188
- CVE-2022-4189
- CVE-2022-4190
- CVE-2022-4191
- CVE-2022-4192
- CVE-2022-4193
- CVE-2022-4194
- CVE-2022-4195
Frequently Asked Questions
1
What is the severity of CVE-2022-4182?
CVE-2022-4182 has a Chromium security severity rating of Medium.
2
How do I fix CVE-2022-4182?
To fix CVE-2022-4182, update Google Chrome to version 108.0.5359.71 or later.
3
What allows attackers to exploit CVE-2022-4182?
CVE-2022-4182 allows attackers to bypass fenced frame restrictions via a crafted HTML page.
4
Which versions of Google Chrome are affected by CVE-2022-4182?
Google Chrome versions prior to 108.0.5359.71 are affected by CVE-2022-4182.
5
Is CVE-2022-4182 specific to any operating system?
CVE-2022-4182 is found in Google Chrome and is not exclusive to any particular operating system.