CVE-2022-3311: Use after free in Import

Reference Links

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

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-3312
• CVE-2022-3313
• 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-3311?

  CVE-2022-3311 has a medium severity rating in terms of Chromium security.

• How do I fix CVE-2022-3311?

  To fix CVE-2022-3311, update Google Chrome to version 106.0.5249.62 or later.

• Which versions of Google Chrome are affected by CVE-2022-3311?

  CVE-2022-3311 affects Google Chrome versions up to and including 106.0.5249.61.

• Can CVE-2022-3311 lead to a sandbox escape?

  Yes, CVE-2022-3311 allows remote attackers to potentially perform a sandbox escape via a crafted HTML page.

• Is there a workaround for CVE-2022-3311?

  The recommended solution for CVE-2022-3311 is to update to the latest version of Google Chrome, as there are no known workarounds.