CVE-2022-2611: Inappropriate implementation in Fullscreen API
Published Apr 28, 2022
·Updated
Inappropriate implementation in Fullscreen API in Google Chrome on Android prior to 104.0.5112.79 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
Credit
Irvan Kurniawan (sourc7)
Affected Software
4 affected componentsFixes available
Google Chrome<104.0.5112.79
104.0.5112.79
Google Chrome<104.0.5112.79
Google Android
fedoraproject fedora=37
Event History
Apr 28, 2022
CVE Published
12:00 AM
Aug 12, 2022
CVE Published
via MITRE·07:36 PM
Data Sourced
via MITRE·07:36 PM
DescriptionWeakness
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
1
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.
2
How do I fix CVE-2022-2611?
To mitigate CVE-2022-2611, update Google Chrome to version 104.0.5112.79 or later.
3
What systems are affected by CVE-2022-2611?
CVE-2022-2611 affects Google Chrome versions prior to 104.0.5112.79 on Android devices.
4
What type of vulnerability is CVE-2022-2611?
CVE-2022-2611 is a spoofing vulnerability associated with the Fullscreen API implementation.
5
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.