CVE-2022-2616: Inappropriate implementation in Extensions API

Reference Links

• https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop.html (Advisory)
• https://crbug.com/1302159
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/
• https://security.gentoo.org/glsa/202208-35
• https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/

Parent vulnerabilities

(Appears in the following advisories)

• 849835485002254358

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-2603
• CVE-2022-2604
• CVE-2022-2605
• CVE-2022-2606
• CVE-2022-2607
• CVE-2022-2608
• CVE-2022-2609
• CVE-2022-2742
• CVE-2022-2743
• CVE-2022-2610
• CVE-2022-2611
• CVE-2022-2612
• CVE-2022-2613
• CVE-2022-2614
• CVE-2022-4914
• CVE-2022-2615
• CVE-2022-2617
• CVE-2022-2618
• CVE-2022-2619
• CVE-2022-2620
• CVE-2022-2621
• CVE-2022-2622
• CVE-2022-2623
• CVE-2022-2624

Frequently Asked Questions

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

  CVE-2022-2616 has been classified with a moderate severity level due to its potential to allow malicious spoofing of the Omnibox in Google Chrome.

• How do I fix CVE-2022-2616?

  To fix CVE-2022-2616, update Google Chrome to version 104.0.5112.79 or later.

• What systems are affected by CVE-2022-2616?

  CVE-2022-2616 affects Google Chrome versions prior to 104.0.5112.79 and Fedora 37.

• What can an attacker do with CVE-2022-2616?

  An attacker can spoof the Omnibox contents by convincing a user to install a malicious extension.

• When was CVE-2022-2616 disclosed?

  CVE-2022-2616 was disclosed in August 2022 alongside the respective Chrome update.