CVE-2022-2853: Heap buffer overflow in Downloads

Reference Links

• http://packetstormsecurity.com/files/169459/Chrome-offline_items_collection-OfflineContentAggregator-OnItemRemoved-Heap-Buffer-Overflow.html
• https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop_16.html (Advisory)
• https://crbug.com/1350097
• 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-2857
• CVE-2022-2858
• 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-2853?

  CVE-2022-2853 has a severity rating that indicates a heap buffer overflow could lead to potential exploitation by remote attackers.

• How do I fix CVE-2022-2853?

  To fix CVE-2022-2853, you should update Google Chrome to version 104.0.5112.101 or later.

• What systems are affected by CVE-2022-2853?

  CVE-2022-2853 affects Google Chrome for Android prior to version 104.0.5112.101.

• What type of vulnerability is CVE-2022-2853?

  CVE-2022-2853 is classified as a heap buffer overflow vulnerability.

• Can CVE-2022-2853 be exploited remotely?

  Yes, CVE-2022-2853 can potentially be exploited by a remote attacker if the renderer process is compromised.