CVE-2022-3313: Incorrect security UI in Full Screen

Reference Links

• https://chromereleases.googleblog.com/2022/09/stable-channel-update-for-desktop_27.html (Advisory)
• https://crbug.com/1317904
• https://security-tracker.debian.org/tracker/CVE-2022-3313

Parent vulnerabilities

(Appears in the following advisories)

• 8820382610464526564

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-3304
• CVE-2022-3201
• CVE-2022-3305
• CVE-2022-3306
• CVE-2022-3307
• CVE-2022-3308
• CVE-2022-3309
• CVE-2022-3310
• CVE-2022-3311
• CVE-2022-3312
• CVE-2022-3314
• CVE-2022-3315
• CVE-2022-3316
• CVE-2022-3317
• CVE-2022-3318
• CVE-2022-3443
• CVE-2022-3444
• CVE-2022-4911

Frequently Asked Questions

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

  CVE-2022-3313 has a medium severity rating according to Chromium security assessments.

• How do I fix CVE-2022-3313?

  To fix CVE-2022-3313, update Google Chrome to version 106.0.5249.62 or higher.

• 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.

• Can CVE-2022-3313 be exploited?

  Yes, CVE-2022-3313 allows a remote attacker to spoof security UI through a crafted HTML page.

• What platforms are impacted by CVE-2022-3313?

  CVE-2022-3313 impacts Google Chrome on all platforms and certain Debian packages of Chromium.