CVE-2022-1868: Inappropriate implementation in Extensions API

Reference Links

• https://chromereleases.googleblog.com/2022/05/stable-channel-update-for-desktop_24.html (Advisory)
• https://crbug.com/1301203
• 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-1862
• CVE-2022-4918
• CVE-2022-1863
• CVE-2022-1864
• CVE-2022-1865
• CVE-2022-1866
• CVE-2022-1867
• 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 vulnerability ID for this Chrome vulnerability?

  The vulnerability ID for this Chrome vulnerability is CVE-2022-1868.

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

  The severity of CVE-2022-1868 is medium with a CVSS score of 6.5.

• What software is affected by CVE-2022-1868?

  Google Chrome versions prior to 102.0.5005.61 are affected by CVE-2022-1868.

• How can an attacker exploit CVE-2022-1868?

  An attacker who convinces a user to install a malicious extension can exploit CVE-2022-1868 to bypass navigation restrictions via a crafted HTML page.

• Is there a fix available for CVE-2022-1868?

  Yes, a fix for CVE-2022-1868 is available in Google Chrome version 102.0.5005.61 and later.