CVE-2022-3313: Incorrect security UI in Full Screen
Published Apr 20, 2022
·Updated
Incorrect security UI in full screen in Google Chrome prior to 106.0.5249.62 allowed a remote attacker to spoof security UI via a crafted HTML page. (Chromium security severity: Medium)
Credit
Irvan Kurniawan (sourc7)
Affected Software
3 affected componentsFixes available
debian/chromium<=90.0.4430.212-1~deb10u1
116.0.5845.180-1~deb11u1120.0.6099.109-1~deb11u1119.0.6045.199-1~deb12u1120.0.6099.109-1~deb12u1120.0.6099.109-1
Google Chrome<106.0.5249.61
106.0.5249.61
Google Chrome<106.0.5249.62
Event History
Apr 20, 2022
CVE Published
12:00 AM
Nov 1, 2022
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeaknessAffected Software
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
1
What is the severity of CVE-2022-3313?
CVE-2022-3313 has a medium severity rating according to Chromium security assessments.
2
How do I fix CVE-2022-3313?
To fix CVE-2022-3313, update Google Chrome to version 106.0.5249.62 or higher.
3
Which versions are affected by CVE-2022-3313?
CVE-2022-3313 affects Google Chrome versions up to 106.0.5249.61 and various Debian packages of Chromium up to 90.0.4430.212-1~deb10u1.
4
Can CVE-2022-3313 be exploited?
Yes, CVE-2022-3313 allows a remote attacker to spoof security UI through a crafted HTML page.
5
What platforms are impacted by CVE-2022-3313?
CVE-2022-3313 impacts Google Chrome on all platforms and certain Debian packages of Chromium.