CVE-2022-2857: Use after free in Blink

Reference Links

• https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop_16.html (Advisory)
• https://crbug.com/1338135
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/
• https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/

Parent vulnerabilities

(Appears in the following advisories)

• 5720220590878638492

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-2852
• CVE-2022-2854
• CVE-2022-2855
• CVE-2022-2858
• CVE-2022-2853
• CVE-2022-2856
• CVE-2022-2998
• CVE-2022-2859
• CVE-2022-2860
• CVE-2022-2861

Frequently Asked Questions

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

  CVE-2022-2857 is classified as a high severity vulnerability due to its potential to exploit heap corruption in Google Chrome.

• How do I fix CVE-2022-2857?

  To fix CVE-2022-2857, update Google Chrome to version 104.0.5112.101 or later.

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

  CVE-2022-2857 affects all versions of Google Chrome prior to 104.0.5112.101.

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

  There are no known workarounds for CVE-2022-2857, and the best course of action is to apply the software update.

• Can CVE-2022-2857 be exploited remotely?

  Yes, CVE-2022-2857 allows a remote attacker to potentially exploit the vulnerability via a carefully crafted HTML page.