CVE-2022-1862: Inappropriate implementation in Extensions

Reference Links

• https://chromereleases.googleblog.com/2022/05/stable-channel-update-for-desktop_24.html (Advisory)
• https://crbug.com/1236325
• https://security.gentoo.org/glsa/202208-25

Parent vulnerabilities

(Appears in the following advisories)

• 1503472642066069577

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-1853
• CVE-2022-1854
• CVE-2022-1855
• CVE-2022-1856
• CVE-2022-1857
• CVE-2022-1858
• CVE-2022-1859
• CVE-2022-1860
• CVE-2022-1861
• CVE-2022-4918
• CVE-2022-1863
• CVE-2022-1864
• CVE-2022-1865
• CVE-2022-1866
• CVE-2022-1867
• CVE-2022-1868
• CVE-2022-1869
• CVE-2022-1870
• CVE-2022-1871
• CVE-2022-1872
• CVE-2022-1873
• CVE-2022-1874
• CVE-2022-1875
• CVE-2022-1876

Frequently Asked Questions

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

  CVE-2022-1862 has a high severity rating due to the potential for an attacker to bypass profile restrictions.

• How do I fix CVE-2022-1862?

  You can fix CVE-2022-1862 by updating Google Chrome to version 102.0.5005.61 or later.

• Which versions of Google Chrome are affected by CVE-2022-1862?

  CVE-2022-1862 affects all versions of Google Chrome prior to 102.0.5005.61.

• What does CVE-2022-1862 allow an attacker to do?

  CVE-2022-1862 allows an attacker to bypass profile restrictions by convincing a user to install a malicious extension.

• What steps should I take if I suspect my Google Chrome is vulnerable to CVE-2022-1862?

  If you suspect your Google Chrome is vulnerable to CVE-2022-1862, immediately update to the latest version and remove any suspicious extensions.