CVE-2022-2611: Inappropriate implementation in Fullscreen API

Reference Links

• https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop.html (Advisory)
• https://crbug.com/1320538
• 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-2612
• CVE-2022-2613
• CVE-2022-2614
• CVE-2022-4914
• CVE-2022-2615
• CVE-2022-2616
• 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-2611?

  CVE-2022-2611 has not been assigned a specific CVSS score, but it represents a medium risk due to the potential for spoofing attacks.

• How do I fix CVE-2022-2611?

  To mitigate CVE-2022-2611, update Google Chrome to version 104.0.5112.79 or later.

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

  CVE-2022-2611 affects Google Chrome versions prior to 104.0.5112.79 on Android devices.

• What type of vulnerability is CVE-2022-2611?

  CVE-2022-2611 is a spoofing vulnerability associated with the Fullscreen API implementation.

• Can a remote attacker exploit CVE-2022-2611?

  Yes, a remote attacker can exploit CVE-2022-2611 to spoof the contents of the Omnibox via a crafted HTML page.