CVE-2022-4924: Use after free in WebRTC

Reference Links

• https://chromereleases.googleblog.com/2022/01/stable-channel-update-for-desktop.html (Advisory)
• https://crbug.com/1272967
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PQKT7EGDD2P3L7S3NXEDDRCPK4NNZNWJ/

Parent vulnerabilities

(Appears in the following advisories)

• 3758141203538733592

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-0096
• CVE-2022-0097
• CVE-2022-0098
• CVE-2022-0099
• CVE-2022-0100
• CVE-2022-0101
• CVE-2022-0337
• CVE-2022-0102
• CVE-2022-0103
• CVE-2022-0104
• CVE-2022-0105
• CVE-2022-0106
• CVE-2022-0107
• CVE-2022-0108
• CVE-2022-0109
• CVE-2022-0110
• CVE-2022-0111
• CVE-2022-0112
• CVE-2022-0113
• CVE-2022-0114
• CVE-2022-0115
• CVE-2022-0116
• CVE-2022-0117
• CVE-2022-0118
• CVE-2022-0120
• CVE-2022-4925

Frequently Asked Questions

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

  CVE-2022-4924 has a high severity rating due to the potential for a sandbox escape via a crafted HTML page.

• How do I fix CVE-2022-4924?

  To fix CVE-2022-4924, update Google Chrome to version 97.0.4692.71 or later.

• What does the vulnerability CVE-2022-4924 affect?

  CVE-2022-4924 affects the WebRTC component in Google Chrome prior to version 97.0.4692.71.

• Can CVE-2022-4924 be exploited remotely?

  Yes, CVE-2022-4924 can be exploited remotely by a compromised renderer process.

• Is it necessary to update Chrome for CVE-2022-4924?

  Yes, it is essential to update Chrome to mitigate the risks associated with CVE-2022-4924.