CVE-2022-4182: Inappropriate implementation in Fenced Frames

Reference Links

• https://chromereleases.googleblog.com/2022/11/stable-channel-update-for-desktop_29.html (Advisory)
• https://crbug.com/1368739
• https://security.gentoo.org/glsa/202305-10
• https://security.gentoo.org/glsa/202311-11

Parent vulnerabilities

(Appears in the following advisories)

• 4678397640046356862

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

• What is the severity of CVE-2022-4182?

  CVE-2022-4182 has a Chromium security severity rating of Medium.

• How do I fix CVE-2022-4182?

  To fix CVE-2022-4182, update Google Chrome to version 108.0.5359.71 or later.

• What allows attackers to exploit CVE-2022-4182?

  CVE-2022-4182 allows attackers to bypass fenced frame restrictions via a crafted HTML page.

• 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.

• 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.