CVE-2022-4195: Insufficient policy enforcement in Safe Browsing

Reference Links

• https://chromereleases.googleblog.com/2022/11/stable-channel-update-for-desktop_29.html (Advisory)
• https://crbug.com/1371926
• 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-4182
• 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

Frequently Asked Questions

• What is CVE-2022-4195?

  CVE-2022-4195 refers to an insufficient policy enforcement vulnerability in Safe Browsing in Google Chrome prior to version 108.0.5359.71.

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

  The severity of CVE-2022-4195 is rated as medium (4.3).

• How does CVE-2022-4195 impact Google Chrome users?

  CVE-2022-4195 allows a remote attacker to bypass Safe Browsing warnings via a malicious file, potentially exposing users to harmful content.

• How can I fix CVE-2022-4195?

  To fix CVE-2022-4195, users should update Google Chrome to version 108.0.5359.71 or later, as it contains a fix for this vulnerability.

• Where can I find more information about CVE-2022-4195?

  You can find more information about CVE-2022-4195 at the following references: [link1], [link2], [link3].